fix: require today's ops for today's ops-scenario #1551
Merged
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
I'm not that convinced we need to yank, although not super opposed to it. If someone has moved to 7.1 already and done a more typical update of both ops and ops-scenario then there's no need to break that. |
tonyandrewmeyer
approved these changes
Jan 30, 2025
benhoyt
approved these changes
Jan 30, 2025
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.
and prep for release
the idea is that we'd:
ops-scenario=7.1.1ops-scenario=7.1.0the users can then either stay on old ops and old ops-scenario, or upgrade both
the automatic version resolution should work, I think :)