Fix duplicate releases - #192
Merged
Merged
Conversation
The "check" step only sets a "should_release" output, not "version" - the version comes from the earlier "version" step. Referencing the wrong step left VERSION empty, which made the awk pattern match every "## " changelog header instead of just the target version's, so notes for older releases kept bleeding into newer ones (see v8.6.2 and v8.6.3 release notes).
jamiecobbett
changed the title
jcardozagc
approved these changes
Aug 13, 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.
When a change was pushed down from client-library-templates, the flow in here created 3 releases instead of 1.
They also had the description repeated within each release.
This is because:
steps.check.outputs.versiondoesn't exist — thecheckstep only outputsshould_release. The version comes from theversionstep (steps.version.outputs.version), which is already referenced correctly elsewhere in this file.VERSIONempty, the awk extraction's start pattern (^##+ empty string) matched every version header in CHANGELOG.md, andnextfired before the exit rule ever got a chance to run, so notes from older releases kept bleeding into newer ones.