fix CI npm cache write denied under restricted GITHUB_TOKEN - #59
Merged
Conversation
Publish and integration workflows restrict GITHUB_TOKEN to contents:read, which can restore caches but cannot reserve/write them. That produced the setup-node warning "cache write denied: token has no writable scopes" after a successful 0.2.4 publish. Add actions:write so cache: npm can save. Co-authored-by: ProxyMesh AI <proxymeshai@users.noreply.github.com>
proxymeshai
marked this pull request as ready for review
September 1, 2026 20:45
proxymesh
approved these changes
Sep 1, 2026
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.


Summary
Confirmed npm and JSR both successfully published 0.2.4 (publish job concluded success). The annotation on Post Setup Node was a cache-save warning, not a publish failure:
cache write denied: token has no writable scopesCause
publish.yml(andproxy_integration_tests.yml) set explicit least-privilege permissions with onlycontents: read. That allows cache restore but not reserve/write whenactions/setup-nodeusescache: npm.Fix
Add
actions: writeso setup-node can save the npm cache:.github/workflows/publish.yml.github/workflows/proxy_integration_tests.ymlactionlintpasses on the updated workflows.Slack Thread