ci: bump juju 3.1 -> 3.5 in track/2.1 #241
Closed
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
|
The problem with the CI is that mysql-k8s 8.0/edge requires juju <3.5.0 or ==3.5.2, which hasn't been released. This CI will be blocked until we do either of: a) Use mysql-k8s 8.0/stable - this is problematic because they will soon promote from 8.0/edge, which will leave us with the same issue |
|
I 'd go with a) since I 'd expect taking this requirement into account before promoting edge -> stable, since it's a breaking change in a way. Apart from that:
This way, if they promote and we hit this issue again, we can then consider what we do with the juju version, taking into account what is decided in canonical/bundle-kubeflow#940 |
|
Closing this PR as it will be replaced by #241 |
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.
Part of canonical/bundle-kubeflow#859