When working on a package where a collaborator has already upgraded to roxygen2 8.0.0, it’s possible to end up with both the old and new RoxygenNote entries in DESCRIPTION.
In my case, I still had roxygen2 7.3.3 installed but a collaborator had already upgraded the package documentation to use v8.0.0. Regenerating docs created a bunch of diff noise and added RoxygenNote: 7.3.3 to DESCRIPTION.
I then installed roxygen2 8.0.0 and rebuilt the docs. That removed the documentation diffs, but left the newly added RoxygenNote: 7.3.3 line. Because the file also already had the 8.0.0-era RoxygenNote entry from my collaborator, I think the migration step may have been skipped.
This seems likely to happen in collaborative workflows where one person has already upgraded to roxygen2 8.0.0 and another person regenerates docs before upgrading.
When working on a package where a collaborator has already upgraded to roxygen2 8.0.0, it’s possible to end up with both the old and new
RoxygenNoteentries inDESCRIPTION.In my case, I still had roxygen2 7.3.3 installed but a collaborator had already upgraded the package documentation to use v8.0.0. Regenerating docs created a bunch of diff noise and added
RoxygenNote: 7.3.3toDESCRIPTION.I then installed roxygen2 8.0.0 and rebuilt the docs. That removed the documentation diffs, but left the newly added
RoxygenNote: 7.3.3line. Because the file also already had the 8.0.0-eraRoxygenNoteentry from my collaborator, I think the migration step may have been skipped.This seems likely to happen in collaborative workflows where one person has already upgraded to roxygen2 8.0.0 and another person regenerates docs before upgrading.