Repository navigation
ci: let the standing-PR update post its commit status - #714
Conversation
The jobs that run `standing-pr update` lacked `statuses: write`, so posting the releasekit/standing-pr status failed with a 403 on every run. The consumer template, example and docs already grant it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Standing release PR: #614 · v0.42.0 queued (4 packages) · open 82d 21h 59m · ✅ ready to merge Release Preview — v0.41.2 → v0.41.3
These changes will be added to the release PR (#614) when merged: Changelogmonorepo 0.41.2 → 0.41.3
After merge — predicted release
Updated automatically by ReleaseKit |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| permissions: | ||
| contents: write | ||
| pull-requests: write | ||
| statuses: write |
There was a problem hiding this comment.
All three jobs call _standing-pr-update.reusable.yml, whose own permissions block lists only contents and pull-requests. That block sets unlisted permissions to none, so adding statuses: write here still leaves the called workflow's GITHUB_TOKEN unable to post releasekit/standing-pr.
Add statuses: write to the reusable workflow too. Otherwise all three paths continue logging the same 403 warning without posting their status.
There was a problem hiding this comment.
Right — #714 merged before this commit landed, so the fix is in a follow-up PR: the reusable workflow's own permissions block now grants statuses: write too.
Description
Every
standing-pr updaterun in this repo loggedFailed to post commit status: Resource not accessible by integration(a 403): the three jobs that run it (update-release-prandupdate-on-labelinstanding-pr.yml, the reconcile job inrelease.yml) grantedcontentsandpull-requestsbut notstatuses. So thereleasekit/standing-prstatus never reached the release branch. The consumer template, the standing-PR example andci-setup.mdalready grantstatuses: write; this brings the repo's own workflows in line.Related Issue(s)
None; seen in #614's label-triggered run.
Type of Change
feat— New featurefix— Bug fixdocs— Documentation changerefactor— Code refactoringtest— Adding or updating testschore— Maintenance, dependencies, toolingScope
@releasekit/version@releasekit/notes@releasekit/publish@releasekit/release@releasekit/config@releasekit/coreChecklist
pnpm lint)pnpm test)pnpm typecheck)Testing Notes
Workflow permissions only. The next standing-PR update run should post
releasekit/standing-prwith no 403 warning.🤖 Generated with Claude Code
Add
statuses: writeto the shared reusable workflow before merging so this change fixes the missing commit statuses.Summary
Adds
statuses: writeto the routine update, label-triggered update, and post-release reconcile jobs.Reviews (1) · Last reviewed commit: "ci: let the standing-PR update post its ..." · Reviewed by Greptile