Repository navigation
ci: advance automated merge queues after validation - #83
Merged
Merged
Conversation
Signed-off-by: IanHollow <72767437+IanHollow@users.noreply.github.com>
Signed-off-by: IanHollow <72767437+IanHollow@users.noreply.github.com>
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.
GitHub can create the next merge candidate after the final validation callback exits. Use the verified v2.12.0 shared release so publishing complete successful checks starts bounded discovery and validation of the next candidate automatically. Update general shared CI references together to preserve the existing single-release contract; independent repository validators and SLSA builders retain their reviewed pins.
The release archive checksum, source manifest and all three provenance subjects were verified. Actionlint, workflow contracts and semantic YAML comparison pass; only immutable shared release references change. Required hosted checks and normal merge-group validation remain mandatory.
Merge Danger
Door: two-way
Revert the shared release references to restore the previous implementation.
Blast Radius: repository
Changes automated queue advancement for this repository; native validation and branch protection still apply.