Repository navigation
ci: publish through npm trusted publishing - #125
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
The Release workflow now publishes through npm trusted publishing (OIDC), and not with the
NPM_TOKENsecret.id-token: write. pnpm 11 changes the OIDC token of the job into a short npm token for@human-kit/ui, and it adds the provenance statement.~/.npmrcis removed, and the Publish step no longer getsNPM_TOKENorNODE_AUTH_TOKEN. Without a token, a failed OIDC exchange stops the publish: it does not fall back to an old credential.human-kit/ui, workflowrelease.yml, with direct publish.scripts/publish.mjsmoves the prerelease dist-tag withnpm dist-tag add. Trusted publishing does not authorize that by default, thus a comment says what to do before the next prerelease. The package is not in prerelease mode now.npm marks a new trusted publisher as "pending" until the first publish through it.
🤖 Generated with Claude Code