Add staged npm publishing via GitHub Actions (OIDC)#178
Merged
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
patocallaghan
force-pushed
the
patoc/oidc-staged-publishing
branch
from
879c60e to
5da876c
Compare
ianluddy
approved these changes
Jun 10, 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
2 participants
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.
Migrates npm publishing to a release-triggered GitHub Actions workflow using OIDC trusted publishing (no long-lived npm token) and npm's staged publishing. Stable releases go to the
latestdist-tag; prereleases tonext.Also removes the CircleCI
releasejob (which published viayarn semantic-releaseusing a token). The CircleCItestjob (format / lint / tests) is kept. Pins Node via.nvmrc(a deliberate major bump from the current version).Release-process change: semantic-release previously automated version bump + changelog + publish on merge to the default branch. With it removed, releases are cut as GitHub Releases (the new workflow triggers
on: release), andpackage.json's version must match the release tag. The workflow can't publish until a stage-only Trusted Publisher is registered for the package on npm.semantic-releaseis left as an unused devDependency that can be dropped in a follow-up.