fix(canary): use unique run_id for version identifier #1194
+1
−1
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
github.run_attempt resets to 1 for each new workflow run, causing version collisions when triggering multiple canary releases from the same PR. Switch to github.run_id which is globally unique per workflow run, ensuring each canary publish produces a distinct version.
Contributor
There was a problem hiding this comment.
Pull request overview
This PR fixes a version collision issue in canary releases by switching from github.run_attempt to github.run_id for the prerelease identifier. The previous implementation reset to 1 for each workflow run, causing duplicate versions when multiple canary releases were triggered from the same PR.
Changes:
- Updated the
PRERELEASE_IDvariable construction to usegithub.run_idinstead ofgithub.run_attempt
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
ryanmcafee
approved these changes
Jan 28, 2026
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.
Summary
github.run_attempttogithub.run_idrun_attemptresets to1for every new workflow run, causing version collisions when triggering multiple canary releases from the same PRrun_idis globally unique per workflow run, ensuring each/canary-releaseproduces a distinct npm versionContext
Discovered while testing PR #1188 — repeated
/canary-releasetriggers produced17.2.2-canary-1188-1.0each time, and lerna skipped publishing because the version already existed on npm.Test plan
/canary-releaseon PR feat(PLATENG-800): Replace @lifeomic/alpha with @jupiterone/platform-sdk-fetch #118817.2.2-canary-1188-<run_id>.0)