ci: publish to npm via OIDC trusted publishing#35
Merged
Conversation
Enable npm registry publishing in the release pipeline: - .releaserc.json: drop npmPublish:false so @semantic-release/npm publishes @linqapp/cli on release - release.yml: add id-token:write for OIDC, upgrade npm to >=11.5.1 (trusted publishing requirement), drop the NPM_TOKEN secret - package.json: enable provenance attestations on publish - README: document npm install option
Collaborator
Author
|
🎉 This PR is included in version 2.3.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
What
Enables npm registry publishing for
@linqapp/clithrough the existing semantic-release pipeline, using OIDC trusted publishing — noNPM_TOKENsecret.Changes
.releaserc.json— removednpmPublish: falsefrom@semantic-release/npm, so releases now publish to npm (previously GitHub releases only).release.yml— addedid-token: writepermission for OIDC, added an npm upgrade step (trusted publishing requires npm ≥ 11.5.1; runners ship 10.x), removed the now-unusedNPM_TOKENenv var.package.json— addedpublishConfig.provenance: truefor signed provenance attestations.README.md— documentednpm install -g @linqapp/cli.Committed as
ci:so merging this does not itself trigger a release — leaving time to configure the trusted publisher first.@linqapp/cli@2.2.0was published manually for the initial bootstrap (OIDC can't create a brand-new package). All subsequent releases publish tokenless via OIDC.