This blog is updated daily.
A general description is here.
‘R CMD check’ now also checks for filenames that are case-insensitive matches to Windows' reserved file names with extensions, such as ‘nul.Rd’, as these have caused problems on some Windows systems.
It checks for inefficiently saved ‘data/*.rda’ and ‘data/*.RData’ files, and reports on those large than 100Kb. A more complete check (including of the type of compression, but potentially much slower) can be switched on by setting environment variable ‘_R_CHECK_COMPACT_DATA2_’ to ‘TRUE’.
The types of files in the ‘data’ directory are now checked, as packages are _still_ misusing it for non-R data files.
It now extracts and runs the R code for each vignette in a separate directory and R process. Rather than call ‘tools::checkVignettes()’, it calls ‘tool::buildVignettes()’ to see if the vignettes can be re-built as they would be by ‘R CMD build’. Option ‘--use-valgrind’ now applies only to these runs, and not when running code to rebuild the vignettes. This version does a much better job of suppressing output from successful vignette tests.
The ‘00check.log’ file is a more complete record of what is output to ‘stdout’: in particular contains more details of the tests.
It now check all syntactically valid Rd usage entries, and warns about assignments (unless these give the usage of replacement functions).
‘.tar.xz’ compressed tarballs are now allowed, if ‘tar’ supports them (and setting environment variable ‘TAR’ to ‘internal’ does on all platforms).
‘R CMD build --binary’ is now formally deprecated: ‘R CMD INSTALL --build’ has long been the preferred alternative.
‘scan(sep= , strip.white=TRUE)’ sometimes stripped trailing spaces from within quoted strings. (The real bug in PR#14522.)