Resolve a no-release labelled merge to its own reason instead of no-label - #183
Open
woksin wants to merge 1 commit into
Open
Resolve a no-release labelled merge to its own reason instead of no-label#183woksin wants to merge 1 commit into
woksin wants to merge 1 commit into
Conversation
…abel A merged pull request labelled no-release - the organization's explicit 'this merge deliberately publishes nothing' decision, accepted by the release-intent gate - fell through to the no-label reason, which is the one reason verify-published jobs are told to fail on. Every properly labelled documentation or tooling merge that touched a publish-triggering path went red on main (Cratis/cli run 33155633590 and Cratis/Chronicle.Kotlin run 33155615166 on 2026-08-28). The action now recognizes a configurable no-release-labels input (default no-release) and resolves such merges to a new 'no-release' reason, listed as expected rather than unintended. Suppression wins over a bump label when both are present, since releasing is the irreversible answer to an ambiguity the gate should have rejected.
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.
Problem
A merged pull request labelled
no-release- the organization's explicit this merge deliberately publishes nothing decision, accepted by the shared release-intent gate in Cratis/Workflows - fell through to theno-labelreason, which is exactly the reasonverify-publishedjobs are told to fail on. Result: every properly labelled documentation/tooling merge that touches a publish-triggering path goes red onmain. Seen today (2026-08-28) on Cratis/cli run 33155633590 (PR #119, labelledno-release) and Cratis/Chronicle.Kotlin run 33155615166 (PR #55, labelledno-release).Change
no-release-labelsinput (defaultno-release), consistent with the existing configurable bump labels.no-releasereason, documented as expected rather than unintended - so existingverify-publishedconditions (contains(fromJSON('["no-label", "error"]'), ...)) go green for it with no consumer change.no-releaseand a bump label: the gate should reject that combination before merge, but releasing is the irreversible answer to the ambiguity.action.ymlreason/output docs updated;dist/rebuilt.Verification
yarn typecheck,yarn lint:ci,yarn test(64 files, 130 specs) all pass;distrebuilt withyarn clean && yarn build.