fix(ci): skip release-please on release-commit pushes to avoid tag race - #271
Merged
Conversation
Closed
This was referenced Jul 23, 2026
Merged
avivsinai
added a commit
that referenced
this pull request
Jul 24, 2026
🤖 I have created a release *beep* *boop* --- ## [0.47.0](v0.46.0...v0.47.0) (2026-07-24) ### Features * **wake:** add identity-safe owner-bound lifecycle ([#277](#277)) ([84ea950](84ea950)) ### Bug Fixes * **ci:** skip release-please on release-commit pushes to avoid tag race ([#271](#271)) ([e37067a](e37067a)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
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.
Summary
Root cause
release-please.ymlandrelease.ymlboth run on the merged release commit. The Release Please run can scan beforerelease.ymlcreates the new tag, conclude that no latest release exists, and backfill repository history into a bogus next release PR.Release Please is PR-only here (
skip-github-release: true), so it has no work to perform on the release commit itself. The next conventional commit runs after the tag exists;workflow_dispatchremains available for manual recovery.Accepted residual
If a feature reaches
mainafter Release Please last updated the release PR but before that release PR merges, skipping the release-commit push means the feature waits for the nextmaincommit or a manual dispatch before appearing in the next release PR. This fails quiet and self-heals; it replaces the current behavior of generating a history-replay release PR.Verification
python3 scripts/test_release_please_config.pyyamllint -d '{extends: relaxed, rules: {line-length: disable, truthy: disable}}' .github/workflows/release-please.ymlgo run github.com/rhysd/actionlint/cmd/actionlint@latest .github/workflows/release-please.ymlgit diff --checkmake ciPeer-reviewed by Claude before commit; PASS with the accepted residual above called out explicitly.