CI upgrade tests: separate paths for upgrade v8.0.0 and v9.0.0 #7393
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
Signed-off-by: Shlomi Noach <2607934+shlomi-noach@users.noreply.github.com>
That is correct. |
|
replaced by #7848 |
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.
Description
Yesterday we released https://github.com/vitessio/vitess/releases/tag/v9.0.0. From now on, we want to have CI verify that our PRs have valid upgrade path from
v9.0.0.I'm still keeping upgrade tests for
v8.0.0although I think we may not need to run them anymore? Any code we contribute from now on goes to >v9.0.0version, and therefore should not necessarily be compatible withv8.0.0? cc @deepthiSo now there's two distinct CI tests, one called
upgrade8and one calledupgrade9.Checklist
Impacted Areas in Vitess
Components that this PR will affect: