This may choke on the MIT license url, and that's ok.
[x] devtools::build_readme()
[x] devtools::check_win_devel()
[x] Have maintainer ("cre" in description) check email for problems.
[x] revdepcheck::revdep_check(num_workers = 4).
This may choke, it is very sensitive to the binary versions of packages on a given system. Either bypass or ask someone else to run it if you're concerned.
[x] Update cran-comments.md
[x] PR with any changes (and go through the list again) into dev and run through the list again.
Submit to CRAN:
[x] devtools::submit_cran().
[x] Maintainer approves email.
Wait for CRAN...
[x] If accepted :tada:, move to next steps. If rejected, fix and resubmit.
[x] Open and merge a PR containing any updates made to main back to dev.
[x] usethis::use_github_release(publish = FALSE) (publish off, otherwise it won't push) will create a draft release based on the commit hash in CRAN-SUBMISSION and push a tag to the GitHub repo.
[x] Go to the repo, verify the release notes, and publish when ready.
git pull
ondev
branch.devtools::check(".", manual = TRUE, env_vars = c(NOT_CRAN = "false"))
.git checkout main
git pull
urlchecker::url_check()
.devtools::build_readme()
devtools::check_win_devel()
revdepcheck::revdep_check(num_workers = 4)
.cran-comments.md
dev
and run through the list again.Submit to CRAN:
devtools::submit_cran()
.Wait for CRAN...
main
back todev
.usethis::use_github_release(publish = FALSE)
(publish off, otherwise it won't push) will create a draft release based on the commit hash in CRAN-SUBMISSION and push a tag to the GitHub repo.