Skip to content

fix(ci): serialize release-please runs on consecutive main pushes #173

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sebastiancorrea81 merged 1 commit into from
Aug 11, 2026
+13 −0
Merged

fix(ci): serialize release-please runs on consecutive main pushes #173

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,19 @@ on:
branches:
- main

# Serializes consecutive pushes to main so release-please never has two runs
# racing over the same release PR's state. Without this, two pushes landing
# within the ~45s auto-merge window can overlap: one run merges/creates a
# release PR while another, already mid-flight, 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). cancel-in-progress: false
# queues the newer push instead of cancelling the in-flight one, since
# cancelling could interrupt a release-please run partway through mutating
# GitHub state (tags, releases, PR labels).
concurrency:
group: main-branch-push
cancel-in-progress: false

permissions:
contents: write
pull-requests: write
Expand Down
Loading