Repository navigation
feat(release-it-config): support npm trusted publishing - #336
Merged
Merged
Conversation
Publish the toolkit packages with npm trusted publishing (OIDC) instead of the long-lived NPM_TOKEN secret: - release-it-config: set `npm.skipChecks` so release-it no longer runs `npm whoami` / collaborator checks, which cannot succeed without a token - ci.yml: grant `id-token: write` to the release job, drop the "Authenticate with Registry" step and the NPM_TOKEN env Requires a trusted publisher (FRSOURCE/toolkit, ci.yml) configured on npmjs.com for each package before merging. Co-Authored-By: Claude Fable 5.1 <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.
Migrates the toolkit packages from the
NPM_TOKENsecret to npm trusted publishing (OIDC), same asis-animatedalready does.@frsource/release-it-config:npm.skipChecks: true— release-it'snpm whoami/ collaborator pre-checks can't succeed without a token; publishing still fails loudly on auth problems.ci.yml:id-token: writeon the release job, remove the "Authenticate with Registry" step andNPM_TOKENenv.Before merging, configure a trusted publisher on npmjs.com for each package (
@frsource/eslint-config,@frsource/globals-vitest,@frsource/prettier-config,@frsource/release-it-config,@frsource/semantic-release-config): GitHub Actions, orgFRSOURCE, repotoolkit, workflowci.yml, no environment.🤖 Generated with Claude Code