ci: publish to npm via trusted publishing (OIDC)#24
Merged
Conversation
Replace NPM_TOKEN auth with OIDC trusted publishing so publish tokens never expire again. Add repository metadata to all packages and enable provenance attestation. Refs #23
Member
Author
|
@codex review |
14 tasks
|
Codex Review: Didn't find any major issues. Nice work! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
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 npm publishing from
NPM_TOKENto trusted publishing (OIDC). npm write tokens are now capped at 90 days, so token auth guarantees recurring expiry breakage; OIDC is tokenless and permanent.Changes:
publish.yml:id-token: writepermission, dropNODE_AUTH_TOKENandregistry-url(its.npmrctemplate errors when the env var is unset), publish with--provenance.repositoryfield (required for provenance attestation).Tested:
bun run checkgreen; JSON validity of all package.json files verified.Not tested yet: an actual OIDC publish — requires the trusted-publisher config on npmjs.com first (tracked in #23). Merging is safe: publish only runs on tags/dispatch.
No release-note-worthy product change (packages repo, CI-only behavior).
Refs #23 (slice: PR 1 of 2; PR 2 is the same migration in picklab)