Conversation
- Bump runner to Node 20 (npm 10 required for OIDC and --provenance). - Add id-token: write permission so the workflow can request an OIDC token. - Drop NODE_AUTH_TOKEN; npm publish authenticates via Trusted Publishing. - Add --provenance --access public to the publish step. - Add workflow_dispatch with a force_publish input to re-publish a version without re-tagging (needed to recover from a failed publish like v2.3.0).
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.
Merges PR #9 to
main. The v2.3.0 tag and GitHub Release already exist; this merge only fixes the publish path.After this merges:
release.ymlwill seev2.3.0already tagged and skip every step (baseline run of the new workflow).gh workflow run release.yml -f force_publish=trueto publish v2.3.0 to npm with OIDC + provenance.See PR #9 for details.