Repository navigation
ci: harden auto-merge policy for live mode - #107
Merged
Merged
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Auto-merge policy — SHADOW⛔ Blocked
Human review is required; auto-merge was not requested.
|
Co-authored-by: Cursor <cursoragent@cursor.com>
Member
Author
|
Review blocker fixed in c47c31c: replaced the unref’d |
This branch was successfully deployed
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.
Summary
yaml@2.8.3instead of trusting line regexesverified === false, HTTPS product/signup URLs, and slug/filename parityverifiedkeys, string booleans, malformed YAML, slug mismatch, response headers/streams, and timeout behaviorReviewer follow-up
contents: writeis retained because GitHub native auto-merge requires it together withpull-requests: write. The job still checks out only the trusted base SHA, installs one pinned parser with lifecycle scripts disabled, and never executes contributor code.Safety and rollout
This PR does not enable LIVE mode or alter repository settings.
allow_auto_mergeremains false andAUTO_MERGE_ENABLEDremains absent.After this PR receives independent approval, the one-time owner settings remain:
mainand require pull requests;ValidateandValidate Programschecks;AUTO_MERGE_ENABLED=true.Backtest
Replayed the exact September 20-PR cohort through the hardened parser:
The lower rate is intentional: these two PRs previously relied on downstream CI to catch invalid YAML; the classifier now fails closed itself.
Verification