Skip to content

Publish to npm via OIDC trusted publishing - #68

Merged
iamtraction merged 1 commit into
masterfrom
ci/trusted-publishing
Aug 5, 2026
Merged

Publish to npm via OIDC trusted publishing#68
iamtraction merged 1 commit into
masterfrom
ci/trusted-publishing

Conversation

@iamtraction

Copy link
Copy Markdown
Owner

Switches the release workflow from a long-lived npm_token secret to npm's OIDC trusted publishing: GitHub's id-token authenticates the publish, and npm generates provenance automatically.

  • drops NODE_AUTH_TOKEN and the npm_token secret
  • publishes with --access public

One-time setup required on npmjs.com before the next release: add a trusted publisher for @iamtraction/google-translate -> GitHub Actions, repository iamtraction/google-translate, workflow npm-publish.yml. Once it's set, the npm_token repo secret can be deleted.

馃 Generated with Claude Code

Drop the npm_token secret and authenticate the release with GitHub's OIDC
token, and pass --access public so the provenance attestation is generated.

Requires a trusted publisher configured for the package on npmjs.com
(repo iamtraction/google-translate, workflow npm-publish.yml).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@iamtraction
iamtraction merged commit 63a77be into master Aug 5, 2026
2 checks passed
@iamtraction
iamtraction deleted the ci/trusted-publishing branch August 5, 2026 15:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant