Repository navigation
Align maintainer policy - #484
Merged
Merged
Conversation
imran-siddique
requested review from
a team,
carloshvp,
rajnisht7 and
zohebk8s
as code owners
October 2, 2026 21:23
imran-siddique
enabled auto-merge (squash)
October 2, 2026 21:27
satishaakula
approved these changes
Oct 2, 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
2 participants
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.
Align this repository with the canonical maintainer coverage rollout. The gate reads generated policy from the reviewed base commit, validates it and counts independent current-head human approvals. The initial policy deployment has a fallback pinned to exactly the recorded base SHA; missing policy on any later base fails closed.
Existing specialist CODEOWNERS and governance requirements remain applicable.
Routing and publisher/access verification are recorded centrally. No access grant or new appointment is claimed. Validation: nine Node boundary tests passed and generated snapshots matched the canonical record; weakening security approvals to one caused three failures. Repository CI and independent maintainer review remain required.