1.2.0 release #282
Merged
1.2.0 release #282
Conversation
This file contains hidden or 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
Get NCHS mortality to fetch data by changing expected date col output type to `epiweek`
sync: main -> dev
…ng-checks Turn off endpoint missing checks for `geo_values` and `time_values`, which have defaults
doc: credit Nat as contributor
fix: improve reading of `EPIDATR_USE_CACHE` variable
pkgdown fixes, DEVELOPMENT release notes
…ralize Support "YYYY-MM-DD" format in `date_to_epiweek`
minor test fixes, NEWS, dev link borked
dsweber2
requested review from
brookslogan,
dshemetov and
nmdefries
as code owners
dshemetov
approved these changes
Jun 20, 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
Doing a release. See NEWS for what's changing