fix(ci): serialize release-please runs on consecutive main pushes - #173
Merged
Conversation
Two pushes to main landing within the ~45s auto-merge window let two release-please runs overlap: one merges/creates the release PR while another, already mid-flight with stale state, tries to update the PR that just got merged and fails with "the pull request cannot be reopened". Observed live on 2026-08-07 (PR #169/#170) and previously on nullplatform/tofu-modules#485 with the same signature. Adds the same top-level concurrency group tofu-modules' release.yml already uses, so overlapping pushes queue instead of racing. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
gdrojas
approved these changes
Aug 11, 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.
Problem
Two pushes to
mainlanding close together let tworelease-pleaseruns overlap: one merges/creates the release PR while another run, already mid-flight with stale state, tries to update the PR that just got merged and fails:Observed live on 2026-08-07 (PR #169/#170, ~90s window). Same signature as nullplatform/tofu-modules#485's underlying issue.
Fix
Add the same top-level
concurrencygroup thatnullplatform/tofu-modules'release.ymlalready uses, so overlapping pushes tomainqueue instead of racing.cancel-in-progress: falsebecause cancelling a run mid-flight could interruptrelease-pleasewhile it's mutating GitHub state (tags, releases, labels).Note: this doesn't fully eliminate the class of race seen in tofu-modules#485 (that one happened even with this same concurrency block, from two runs executing back-to-back rather than in parallel) — but it does close the specific parallel-execution case seen here, which is a wider and easier-to-hit window.
🤖 Generated with Claude Code