Support trusted publishing for tag releases - #223
Merged
Conversation
Unify the publish job to handle both main branch (dev) and v* tag (release) publishes using npm trusted publishing with OIDC.
✅ Deploy Preview for grats ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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.
Summary
main-releasejob into a singlepublishjob that handles both main branch andv*tag pushesmainpush: publishes dev version (0.0.0-main-<sha>) with--tag mainv*tag push: publishes the version frompackage.jsontolatestenvironment: CIfield (not configured on npm's trusted publishing settings)Test plan
v*tag triggers the workflow and publishes to npm