New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
packrat: release 0.9.1 #706
Comments
Release PR: #707 |
GH release (from tag): https://github.com/rstudio/packrat/releases/tag/v0.9.1 |
Post-release PR: #708 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Prepare for release
Switch to
main
and pull.Create and switch to a release branch (e.g.
release/<version>
).Update version in
DESCRIPTION
file.Update header and version in
NEWS.md
. confirm recent changes areincluded. (style reference)
Update auto-loaders (from R):
source("R/update.R"); updateInit();
Commit your changes!
git commit -m 'preparing for 0.9.1 release' NEWS.md DESCRIPTION inst
Check current CRAN check results:
https://cran.rstudio.org/web/checks/check_results_packrat.html
Check that all URLs are valid (from R):
Generate a release
.tar.gz
by running the following command from theparent directory of your
packrat
repository:R CMD build packrat
Test the package (also from the parent directory):
R CMD check --as-cran packrat_*.tar.gz
Push the branch to GitHub and let our CI workflow run.
Fix any issues identified by the previous steps. Rinse and repeat.
Submit to CRAN
Submit to CRAN. Cross fingers. https://cran.r-project.org/
Wait for CRAN approval.
Approved by CRAN
Squash-and-merge the
release/<version>
branch back tomain
.Create a git tag for your new release and push that tag.
Create a GitHub release from the tag and include its NEWS.md items as
release notes.
Create a branch to bump for development (e.g.
development/X.Y.Z+1
).Update
NEWS.md
with an "unreleased" version header and run the followingcommand to update
DESCRIPTION
and the auto-loaders:R -f configure.R
Commit your changes!
git commit -m 'preparing for X.Y.Z+1 development' NEWS.md DESCRIPTION inst
Push the
development/X.Y.Z+1
branch to GitHub, create a PR, and let CIrun.
Squash-and-merge the PR with the
development/X.Y.Z.1
changes back tomain
.The text was updated successfully, but these errors were encountered: