ci: publish npm package with trusted OIDC - #13
Merged
Conversation
Grant the publish job an OIDC token, use a supported Node/npm runtime, and remove the long-lived NPM_TOKEN credential.
Pin each release action to the verified commit behind its existing ref and grant GITHUB_TOKEN permissions only to the job that needs them.
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
id-token: writeactions/setup-node@v6, satisfying npm's trusted-publishing runtime requirementNPM_TOKEN/NODE_AUTH_TOKENpublish credentialVerification
actionlint .github/workflows/release.ymlgit diff --checkactions/setup-node@v6resolves to an existing action tagcode-memorypackage exists and targets this repository0.1.2;npm publish --dry-run --access publicpackaged successfullyRequired npm setting
Before this workflow can publish, the
code-memorypackage must have a GitHub Actions trusted publisher formstuart/code-memory, workflowrelease.yml, withnpm publishallowed. That registry-side authentication setting is intentionally not changed by this PR.