Automate maintainer agents integration and prepare human-only releases - #6
Merged
Merged
Conversation
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.
Only Jon personally merges main. Apply that rule even after chat approval, and permit every agent acting for a repository maintainer to integrate checked agents work. Replace the owner-only filter with live write/maintain/admin permission checks for the author and acting account.
Successful agents integration now automatically generates patch notes from the merged change titles and opens a frozen release PR. Existing release batches are preserved. CI runs for main PRs and validates the exact release candidate and patch-note metadata in addition to Windows syntax/binding/contract checks. No main merge, deployment, or model change occurs.
Validation: 10 local core checks, syntax compilation, live maintainer lookup, actual main-target refusal, and rejection of unpinned/nonrelease main candidates. The actual coordinator/notes path will be exercised on this PR after hosted CI passes, with the resulting release PR left for Jon.