Fix trusted local audit publication permission - #1036
Conversation
|
Note Automatic reviews are paused because your team has used its included automatic processing for this billing period (headroom scales with your seat count). You can still comment "Gitar review" to run one anytime, and automatic reviews resume on their own by October 1. Add seats for more headroom. Code Review ✅ Approved🟡 Medium risk Grants the trusted local-audit publisher Review coverageRules No rules evaluated OptionsDisplay: compact → Counting what did not apply, without listing it. Comment with these commands to change the behavior for this request:
Was this helpful? React with 👍 / 👎 | Gitar |
|
Owner gate override for exact head
Applying the documented current-head owner override. After merge, a new exact-head audit must demonstrate normal trusted publication before v1.5.0 canaries or release publication. |
The trusted local-audit publisher successfully verifies sealed reviewer metadata, then fails before creating its reservation comment because the workflow token has only read access to pull requests. GitHub authorizes comments on pull requests through the Pull requests permission even though the REST route is under Issues.
This grants the publication workflow
pull-requests: writealongside its existingissues: write, keeps every other permission unchanged, and updates both generated template mirrors. A focused regression guards the permission in addition to the existing workflow trust-boundary checks.Validation:
The previous immutable candidate is invalidated by this release-critical fix. No tag, package publication, hosted provider session, paid canary, or deployment is performed by this PR.