-
Notifications
You must be signed in to change notification settings - Fork 29
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
Release assertthat 0.2.1 #59
Comments
@jameslamb the stricter checks in |
@hadley thanks for running that, I'll inform the maintainers by email |
@hadley actually wait, I have a (possibly better) idea. I looked at the source code of those four packages, and all of them are doing this:
If we changed So, concretely:
|
Yeah, that'd be great |
created #60 |
@jameslamb CRAN checks picked up a new problem that I missed:
Would you mind doing a PR to them to fix the problem? |
yep no problem. Will link here when I make it |
Created NCEAS/codyn#111. I was able to do it in a way that makes their tests work with both |
Perfect, thanks! |
I see this made it to CRAN. @hadley thanks for doing a release! |
Prepare for release:
devtools::check()
devtools::check_win_devel()
rhub::check_for_cran()
revdepcheck::revdep_check(num_workers = 4)
has_name()
failuresSubmit to CRAN:
usethis::use_version()
cran-comments.md
devtools::submit_cran()
Wait for CRAN...
usethis::use_github_release()
usethis::use_dev_version()
The text was updated successfully, but these errors were encountered: