Repository navigation
Publish to npm via trusted publishing (OIDC) - #59
Merged
Merged
Conversation
Replace the long-lived npm token in the release workflow with GitHub Actions OIDC. Adds the id-token permission, drops the NPM_TOKEN env and the ~/.npmrc write, and moves the release job to Node 22 with npm@latest, since trusted publishing requires npm >= 11.5.1. Adds repository metadata to the published packages, which npm requires when generating provenance, and bumps CI to Node 20. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
🦋 Changeset detectedLatest commit: 7b1daf6 The changes in this PR will be included in the next version bump. This PR includes changesets to release 5 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
philorder
approved these changes
Aug 26, 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.
Replaces the long-lived npm token in the release pipeline with GitHub Actions OIDC Trusted Publishing, so releases authenticate to npm without a stored credential.
Trusted publishers are already configured on npmjs.com for the published packages.
Follow-ups
NPM_TOKENis now unreferenced and can be deleted once a release goes green. KeepNPM_AUTH_TOKEN—build.ymlstill uses it, though this repo has no private dependencies, so that step looks removable in a later change.