Skip to content

Accept the no-release intent in the semver gate - #19

Merged
woksin merged 1 commit into
mainfrom
chore/accept-no-release-intent
Aug 25, 2026
Merged

Accept the no-release intent in the semver gate#19
woksin merged 1 commit into
mainfrom
chore/accept-no-release-intent

Conversation

@woksin

@woksin woksin commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

Ports the org-standard release-intent gate (per release-action/.ai/rules/pull-requests.md, as implemented in cli): no-release joins major/minor/patch as an accepted label, so a PR that changes nothing outward-facing can merge without cutting an empty release. Motivated by today's CI-remediation merges, which had to carry patch for lack of this option and cut unintended releases in four repos. This PR itself carries no-release.

Ports the release-intent gate the organization standardizes on
(release-action/.ai/rules/pull-requests.md, as already implemented in cli):
a pull request that changes nothing outward-facing carries no-release and
merging it publishes nothing. Without this option, configuration-only pull
requests were forced to carry patch, which cut empty releases on merge -
exactly what happened with the 2026-08-25 CI remediation merges.
@woksin
woksin merged commit d7b2e38 into main Aug 25, 2026
1 of 2 checks passed
@woksin
woksin deleted the chore/accept-no-release-intent branch August 25, 2026 21:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant