Repository navigation
ci: grant statuses write in the reusable update workflow too - #716
Merged
Merged
Conversation
Its own permissions block sets anything unlisted to none, so the callers' grant alone didn't reach the token. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
|
Standing release PR: #614 · v0.42.0 queued (4 packages) · open 82d 22h 3m · ✅ 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 |
Merged
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.
Description
Follow-up to #714, which merged before this landed. The reusable update workflow has its own
permissionsblock (contents,pull-requests), which sets anything unlisted tonone, so thestatuses: writeits callers now grant never reaches the token. Without this thereleasekit/standing-prstatus still fails with a 403. Found by Greptile on #714.Related Issue(s)
Follow-up to #714.
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
The permission change appears safe to merge.Summary
Adds
statuses: writeto the reusable standing-PR update workflow.No actionable issues found. Workflow execution was not tested.
Reviews (1) · Last reviewed commit: "ci: grant statuses write in the reusable..." · Reviewed by Greptile