Update charm-refresh to v3.0.0.3 #1008
Merged
Conversation
This file contains hidden or 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
Fixes UX bug: canonical/charm-refresh@80c7d80 Ideally, this should be included before the first stable release (so that if the user accidentally refreshes to the charm revision with the first stable release from a different track, they see the correct error message & so that the leader + highest number unit do not go into error state). However, it's not essential to include this in the first stable release.
carlcsaposs-canonical
requested review from
taurus-forever,
dragomirp and
marceloneppel
taurus-forever
approved these changes
Jun 29, 2025
dragomirp
approved these changes
Jun 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.
Fixes UX bug: canonical/charm-refresh@80c7d80
Ideally, this should be included before the first stable release (so that if the user accidentally refreshes to the charm revision with the first stable release from a different track, they see the correct error message & so that the leader + highest number unit do not go into error state). However, it's not essential to include this in the first stable release.