Skip to content
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

Merged
merged 4 commits into from
Oct 29, 2024
Merged

19.1.x with master #3847

merged 4 commits into from
Oct 29, 2024

Conversation

npauzenga
Copy link
Contributor

Summary: Summary of changes

Addresses CUMULUS-XX: Develop amazing new feature

Changes

  • Detailed list or prose of changes
  • ...

PR Checklist

  • Update CHANGELOG
  • Unit tests
  • Ad-hoc testing - Deploy changes and test manually
  • Integration tests

npauzenga and others added 4 commits October 22, 2024 10:37
* 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>
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
Copy link
Member

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?

Copy link
Contributor Author

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.

Copy link
Member

@Jkovarik Jkovarik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. 💯

@npauzenga npauzenga merged commit 5246281 into master Oct 29, 2024
3 checks passed
@npauzenga npauzenga deleted the 19.1.x-with-master branch October 29, 2024 14:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants