ci: migrate npm publishing to OIDC trusted publishing - #39
Open
upsetbit wants to merge 2 commits into
Open
Conversation
Drop the long-lived NPM_TOKEN: remove NODE_AUTH_TOKEN from the publish step and rely on npm OIDC trusted publishing (npm upgraded to >= 11.5.1 in-job). Move the build matrix and publish job to GitHub-hosted runners, required for both the OIDC token exchange and provenance. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <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.
What & why
Replace the long-lived
NPM_TOKENin the npm release with npm OIDC trusted publishing (GA'd 2025-07-31). The GitHub Actions job exchanges a short-lived id-token for publish credentials — no stored secret — and provenance is issued automatically.Changes (
release-npm.yml)NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}from the publish step.npm install -g npm@lateststep (trusted publishing needs npm ≥ 11.5.1; Node's bundled npm may be older).ubuntu-latest/macos-latest/windows-latest). OIDC trusted publishing and provenance are only available on GitHub-hosted runners; standardizing the whole release there (Blacksmith stays for CI).--use-napi-crossis unchanged.permissions: id-token: writewas already present.--provenance/--ignore-scriptskept as-is.The trusted publisher must be registered on npm for all 7 packages first, otherwise the tokenless publish fails:
@c3-oss/codexcw+-darwin-arm64,-darwin-x64,-linux-arm64-gnu,-linux-x64-gnu,-linux-x64-musl,-win32-x64-msvc— repoc3-oss/codexcw, workflowrelease-npm.yml. Run the org-widesetup-trusted-publishers.sh(usesnpm trust github).Suggested validation: cut a pre-release tag (e.g.
node-v<next>-rc1) and confirm the publish job is green with a provenance badge and noNPM_TOKENuse. Keep theNPM_TOKENsecret until validated, then it can be deleted.🤖 Generated with Claude Code