Add tag-driven npm release workflow (trusted publishing)#2
Merged
Conversation
Pushing a crypto-v* tag runs the full suite, verifies the tag matches packages/crypto's version, and publishes via npm OIDC trusted publishing — no stored token, automatic provenance attestations (publishConfig.provenance now takes effect instead of fighting local publishes). Requires the one-time Trusted Publisher configuration on npmjs.com (repo ddyy/pk, workflow release-crypto.yml), documented in the workflow header.
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.
Pushing a
crypto-v*tag now runs the full suite, verifies the tag matchespackages/crypto's version, and publishes via npm OIDC trusted publishing — no stored token, automatic provenance attestations, andpublishConfig.provenance: truefinally takes effect instead of fighting local publishes.One-time setup required on npmjs.com before the next release (documented in the workflow header): package Settings → Trusted Publisher → GitHub Actions → repository
ddyy/pk, workflowrelease-crypto.yml.Replaces the local
npm publish --provenance=false+ OTP flow used for 0.1.0.