Closed hfrick closed 2 years ago
Let us see if mode: auto
can save us. It should have been set anyways. If not then we can try some magic
If we wanted, since the release just happened, we could set the DESCRIPTION
back to 0.2.0 in this PR, merge it, let pkgdown build, and then change back to 0.2.0.9000. I say yes, let's do this.
This pull request has been automatically locked. If you believe you have found a related problem, please file a new issue (with a reprex: https://reprex.tidyverse.org) and link to this issue.
The pkgdown site currently shows
0.2.0.9000
as the release version and0.1.3.9000
as the development version. Should we try some git magic or let the auto dev mode sort that out with the next release? The content of the release site should identical with that of the release0.2.0
because it only just happened. (And the content of the dev version gets updated with the next PR, no?)