-
Notifications
You must be signed in to change notification settings - Fork 5
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
v1.1.1 release #265
Merged
v1.1.1 release #265
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* rebuild it with `devtools::render_readme()` * easier to track changes / multiple files * Note that the rebuilt figure looks a bit different.
Djm/pkgdown updates
A few more fixes for release
Moves the API key documentation to a central spot that is easy to point users to. Edits the warning message to point here, so we don't repeat the key advice in different places. Expand description of how to set options or environment variables.
Better document API keys
ci: remove release helper
fix+chore: version bump, fix #177
post-cran updates
fix: cache size integer overflow
lint: update lintr
style: use glue for line-wrapping in cache warnings
fix: actual license details
1.1.0 pre-CRAN cleanup
CI: docs also includes the readme
ci: document readme and add trigger buttons to all actions
Co-authored-by: David Weber <[email protected]>
If `as_of` sent to `check_is_recent` is a `Date`, compare to a `Date` threshold.
ci: fix pkgdown
ci: fix pkgdown and improve colors
CRAN submission
dsweber2
approved these changes
Mar 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist
Please:
PR).
brookslogan, dshemetov, nmdefries, dsweber2.
DESCRIPTION
. Always incrementthe patch version number (the third number), unless you are making a
release PR from dev to main, in which case increment the minor version
number (the second number).
(backwards-incompatible changes to the documented interface) are noted.
Collect the changes under the next release number (e.g. if you are on
1.7.2, then write your changes under the 1.8 heading).
Change explanations for reviewer
Too hard to drop v1.1.1 commits from dev, just going to skip v1.1.0 release.
Magic GitHub syntax to mark associated Issue(s) as resolved when this is merged into the default branch