Repository navigation
fix(release): validate stable integration through native merge queue - #55
Merged
Merged
Conversation
…le-release-queue # Conflicts: # docs/governance.md
choskeli
marked this pull request as ready for review
October 28, 2026 02:45
This was referenced Oct 28, 2026
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
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.
A release PR can pass a long CI run and become behind
mainagain before merging. Repeated Update branch clicks restart that work. This proposes GitHub's native merge queue so GitHub validates the integrated candidate and later PRs wait behind it.merge_group: checks_requestedto both required workflows. CI concurrency identifies the exact queue SHA. The title check reads paginated PR metadata, bindsmergeQueueEntry.headCommitandbaseCommitto the event, and rejects missing, changed, duplicate, or invalid candidates without checking out PR code.SQUASH,ALLGREEN, one candidate building/merging, no batch wait, 180-minute timeout. Extend the required-check contract and fixtures so a missing or filtered queue check fails before activation.Release Please keeps updating real version/changelog changes. A changed release PR or failed check requires fresh checks/requeueing; ordinary main advancement no longer requires manual branch updates after queue activation. The maintainer enqueues using their existing account:
GITHUB_TOKENcannot enqueue, and this adds no credentials or automatic enqueue bot. Initial bot-generated checks may still require a close/reopen and workflow-execution decision.Review and hosted status
Current head:
b3078298447e0581a477c939b7461594217d10b0, based on main0cea08d0e3d6bd96155badacc9cdb21ad262d5c6; tree49cd37e701ecb7adaa990fc72c968cca7e6c878f. The PR is conflict-free, up to date with this main commit, and remains draft for final parent review. Required hosted checks passed.All checks, PR title and CodeQL passed. All 11 cold mutation partitions and the collected audit passed: 1,289 mutants, 100% adjusted.553cd119a3a31384fc0d365b6103ad301297fd3ebinds current main and this head and has the identical reviewed source tree49cd37e701ecb7adaa990fc72c968cca7e6c878f.25bb6d7passed CI run 40609199752, includingAll checksand parser mutation (29m20s). Its independent review verified 644 tooling tests, 32 mocked Terraform policies and valid candidate acceptance plus 13 invalid metadata cases. Earlier-head successes do not substitute for the current head's required checks.Local evidence on the final head
npm run checkwas not repeated: earlier sandbox HTTP restrictions and Windows-incompatible Linux shell fixtures were documented, with the prior hosted Linux run passing. Required hosted validation passed for this final head. No additional local full mutation campaign was launched.Activation remains separate
Merging this PR does not activate the queue. After merge, explicitly authorize and review a Terraform plan updating existing main ruleset 25840882, then approve/apply it. Do not create a duplicate ruleset. Verify two ordinary PRs queue/merge FIFO without branch updates and that failed checks block, including the real ephemeral-token metadata path. Do not publish a release during acceptance. The current strict-update behavior remains until activation.
This follows GitHub's supported queue model, the pinned Release Please action's own queue CI, and provider 6.13.0 support. A stable release branch would add branch/backport policy and change the existing main-ancestor publisher contract; it is unnecessary for this integration problem.