Skip to content

ci(release): break infinite-loop chain on auto-bump merges#276

Merged
bradtaylorsf merged 1 commit into
masterfrom
chore/release-workflow-loop-guard
May 26, 2026
Merged

ci(release): break infinite-loop chain on auto-bump merges#276
bradtaylorsf merged 1 commit into
masterfrom
chore/release-workflow-loop-guard

Conversation

@bradtaylorsf
Copy link
Copy Markdown
Owner

URGENT: Each auto-generated bump-PR merge currently triggers another release, generating another bump-PR. This adds a guard at the start of 'Determine version' that detects the bot's bump-back commit pattern and skips the release.

Regex matches both 'chore(release): bump version to v2.0.3' (raw) and 'chore(release): bump version to v2.0.3 (#274)' (squash-merged form). Other chore: commits and the original feat!: release commits are unaffected.

The post-publish commit-back step creates a chore(release): bump version
to vX.Y.Z PR; merging that PR is a push to master, which triggers ANOTHER
release run, which publishes vX.Y.(Z+1) and creates ANOTHER bump-PR.
Repeats forever.

This adds a guard at the top of Determine version: if the latest commit
matches the bot's bump-back subject pattern, set skip=true and exit
before any version computation. The rest of the workflow short-circuits
via the existing 'if: steps.version.outputs.skip != true' guards.

Regex covers both the raw form ('chore(release): bump version to v2.0.3')
and the GitHub-squash-merge-decorated form ('... (#274)').
@bradtaylorsf bradtaylorsf merged commit ddb9de0 into master May 26, 2026
3 checks passed
@bradtaylorsf bradtaylorsf deleted the chore/release-workflow-loop-guard branch May 26, 2026 22:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant