@node News
+@cindex news
@unnumbered News
+@anchor{Release 1_27_1}
+@section Release 1.27.1
+@itemize
+@item
+ Fixed lack of @file{.redo.}-prefix in temporary file names.
+@end itemize
+
+@anchor{Release 1_27_0}
+@section Release 1.27.0
+@itemize
+@item
+ Improved out-of-date check and @file{.do} files search performance,
+ because of caching their results.
+@end itemize
+
+@anchor{Release 1_26_0}
+@section Release 1.26.0
+@itemize
+@item
+ Debug output contained colour-related attribute even if
+ @env{$NO_COLOR=1} was set.
+@item
+ Updated dependant libraries.
+@end itemize
+
+@anchor{Release 1_25_0}
+@section Release 1.25.0
+@itemize
+@item
+ Target's lock file requires a token from the jobserver now. So
+ amount of simultaneously opened lock files depends on job slots
+ available.
+@end itemize
+
+@anchor{Release 1_24_0}
+@section Release 1.24.0
+@itemize
+@item
+ @command{redo-cleanup tmp} also removes temporarily (@code{$3})
+ created directories.
+@end itemize
+
+@anchor{Release 1_23_0}
+@section Release 1.23.0
+@itemize
+@item
+ @command{redo-ifchange}'s @option{-f} option forces each target
+ rebuilding. Comparing to @command{redo}, it will parallelize the
+ process.
+@item
+ Inode's number is also stored as dependency information, just to
+ prevent possible @code{ctime} collision of two files.
+@item
+ Performance optimization: do not use target's temporary output file
+ at all, if its hash equals to already existing target's one. Just
+ touch existing target file instead.
+@end itemize
+
@anchor{Release 1_22_0}
@section Release 1.22.0
@itemize
corresponding targets has the same content but different
@code{ctime}/@code{mtime} values and rewrites dependencies with that
updated inode information.
+@item
+ With @env{$REDO_STOP_IF_MODIFIED=1} environment variable redo will
+ stop and fail if it meet externally modified file. By default user
+ is only warned about it, but building continues for convenience.
@end itemize
@anchor{Release 1_21_0}