ci: add OIDC-based npm publish workflow for tagged releases#8
Merged
Conversation
Copilot created this pull request from a session on behalf of
hustcc
July 14, 2026 14:15
View session
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
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.
This PR adds an OIDC trusted publishing path for npm releases, aligned with the
v*.*.*tag-based release flow. It introduces a dedicated publish workflow modeled after the referenced pattern, without token-based npm auth.Release trigger and scope
.github/workflows/publish.yml.v*.*.*to isolate publish behavior to versioned releases.OIDC trusted publishing setup
id-token: writecontents: readnpm publish --provenance --access public.Publish pipeline