-
Notifications
You must be signed in to change notification settings - Fork 107
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
19.1.x with master #3847
19.1.x with master #3847
Conversation
* version bump * Update CL * Update docs * Update CL link * Add note for clarity * update missed deps
* guarantee non-numeric nonNumericString * bringing in pg8.13 snyk suggestion * trying to kcik up the sync-granules task error * trying to get repeatable tries to sync-granules * focus on just the important part in syncgranule * trying to get publish to work * does only this need to change to import? * move to import function import * reverting bad code for testing reasons * changelog * keep string length the same, no reason to twiddle this Co-authored-by: etcart <37375117+etcart@users.noreply.github.com>
@@ -8141,7 +8158,8 @@ Note: There was an issue publishing 1.12.0. Upgrade to 1.12.1. | |||
|
|||
## [v1.0.0] - 2018-02-23 | |||
|
|||
[Unreleased]: https://github.com/nasa/cumulus/compare/v19.0.0...HEAD | |||
[Unreleased]: https://github.com/nasa/cumulus/compare/v19.1.0...HEAD | |||
[v19.1.0]: https://github.com/nasa/cumulus/compare/v19.0.0...v19.1.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not blocking given the PR, but should we do something like 18.5->19.1 in the future given the migration path doesn't travel through 19.0?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The stance I'm taking with v19 is that it exists but is deprecated. So the CL entry for 19.1 has:
This release contains changes listed here as well as changes listed in v19.0.0,
despite v19.0.0 being deprecated. Please review Changelog entries and Migration Notes for
each Cumulus version between your current version and v19.1.0 as normal.
My sense is that it would be more confusing to skip a version here an elsewhere. I could be wrong though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. 💯
Summary: Summary of changes
Addresses CUMULUS-XX: Develop amazing new feature
Changes
PR Checklist