chore(template): release.yml — concurrency + checkout@v5#56
Merged
Conversation
This was referenced May 27, 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
1 participant
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.
Two fixes for new repos scaffolded from this template:
concurrency: release-${{ github.ref }}withcancel-in-progress: false— concurrent merges to main were causing FerrFlow release runs to race and the loser hitE2006: tag already exists pointing at different commit. Queuing release runs avoids this.actions/checkoutfrom v6 to v5 — v6 dropsGITHUB_TOKENon deep fetches (fetch-depth: 0), same regression we patched in fix(security-scan): pin actions/checkout to v5 #51.Existing repos that copied this template still need the same patch applied — see follow-up issue.