Revdep update

Author: hadley

revdep/README.md

@@ -10,4 +10,4 @@ revdep_check(threads = 6, skip = to_skip)
 revdep_check_save_summary()
 revdep_check_print_problems()
 
-# revdep_email(date = "Nov 4", only_problems = TRUE, draft = FALSE)
+# revdep_email(date = "Nov 4", version = "2.2.0", only_problems = TRUE, draft = FALSE)

revdep/check.R

@@ -1,6 +1,6 @@
 Hi,
 
-This is an automated email to let you know about the upcoming release of {{{ my_package }}}, which will be submitted to CRAN on in early November. I'm aiming for {{{ date }}}, but that date may move backwards if significant problems are uncovered. To check for potential problems, I ran `R CMD check` on your package {{{your_package}}} ({{{your_version}}}). 
+This is an automated email to let you know about the upcoming release of {{{ my_package }}}, which will be submitted to CRAN next week. I'm aiming for {{{ date }}}, but that date may move backwards if significant problems are uncovered. To check for potential problems, I ran `R CMD check` on your package {{{your_package}}} ({{{your_version}}}). 
 
 I found: {{{your_summary}}}.
 
@@ -9,6 +9,8 @@ I found: {{{your_summary}}}.
 
 If I got an ERROR because I couldn't install your package (or one of it's dependencies), my apologies. Unfortunately I don't have the time to diagnose installation failures so you'll need to run the check yourself.
 
+Compared to the last set of checks, there is one big change: I discovered a major issue with ggproto which made it unexpectedly fragile. I have fixed the bug, but any package that provides an extension will need to be rebuilt. I will ask CRAN to do this for all packages on CRAN, but when checking your own package you will need to do it yourself.
+
 Otherwise, please determine if this is a problem with my code or your code.  If you think it's a problem with {{ my_package}}, please file an issue on github that attempts to recreate the problem with as little code as possible. If it's a problem with your code, please prepare an updated package for CRAN as soon as possible. The ERRORs and WARNINGs might not be caused by the update to {{{my_package}}}, but it really makes life easier (for both me and CRAN) if you also fix any other problems that may have accumulated over time. Please also try to minimise the NOTEs. It's not essential you do this, but the fewer the false positives the more likely we are to detect a real problem with your package. 
 
 To get the development version of {{{ my_package }}} so you can run the checks yourself, you can run: