fix(release): repair post-merge publication gates - #45
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
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.
Problem
Two live post-merge publication gates fail on valid canonical evidence:
33539105762requestsbranchProtectionRulewith the defaultGITHUB_TOKEN, but GitHub requires unavailable Administration read access.33539105742receivesrun.pull_requests: []after the merged head branch is deleted.Fix
Remove the Administration-gated branch-protection reads while retaining canonical repository, ref, live head, and direct exact-check proofs. Remove only the unstable Actions run pull-request-array predicate from merged changelog proof.
The unique merge-SHA-associated PR, exact PR base/head identity, check, app, suite, details-URL run id, workflow run, repository ids, and workflow path remain directly cross-bound. All five environment-only App-token REST and GraphQL ruleset audits remain exact and adjacent to their protected mutations.
Publication policy revision 2 records the new workflow bytes while preserving revision 1 for historical verification.
Verification
npm run test:pylon-release— 10 passednpm run test:pylon-publication— 33 passednpm run test:pylon-ruleset-auditor-app— 6 passednpm run checkactionlinton the changed workflowsgithub-scriptbodies compiledgit diff --checkverifiedModel: OpenAI Codex GPT-5.6
Harness: Prime Agent
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.