Fix release PR body wording for drifted CLI version#53
Merged
Conversation
axelniklasson
approved these changes
Jun 23, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The release script's PR body assumed that whenever the action version and default CLI version differ, the CLI version was unchanged — printing "default CLI version stays at vX". That's wrong when the CLI default drifts and moves in the same release (e.g. action
0.14.5, CLI0.14.2→0.14.3): it read "stays at v0.14.3" even though v0.14.3 was new.This captures the previous CLI default from
action.ymlbefore the bump and compares against it, so the body now distinguishes three cases:Bumps the action and default CLI version to vX.... (default CLI version stays at vY).... (default CLI version bumped to vY).