fix(ci): grant contents write permission for beachball publish push#229
Merged
frantic1048 merged 1 commit intomainfrom Mar 20, 2026
Merged
fix(ci): grant contents write permission for beachball publish push#229frantic1048 merged 1 commit intomainfrom
frantic1048 merged 1 commit intomainfrom
Conversation
When `id-token: write` was added for trusted npm publishing (OIDC), specifying `permissions` at the job level overrides all defaults. `contents` dropped from `write` to `read`, breaking beachball's `git push` after publish. Also syncs package version to 1.5.3 (already published) and removes the 3 consumed changefiles. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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.
Summary
contents: read→contents: writein thebuildjob permissions so beachball can push its version bump commit after publishingpackage.jsonversion to 1.5.3 (already published to npm) usingbeachball syncpin-beachball-action, type:none— won't trigger a publish)Context
When
id-token: writewas added for OIDC npm publishing, specifyingpermissionsat the job level overrides all defaults.contentsdropped fromwrite(the GitHub Actions default) toread, breaking beachball'sgit pushafter publish.Test plan
beachball checkshould pass since the remaining changefile has typenone)Publish (main)CI job should skip publishing (no publishable changefiles) and succeed🤖 Generated with Claude Code