fix: add tag for pre release (@next) vs release (@latest)#491
Open
lwasser wants to merge 1 commit intoall-contributors:mainfrom
Open
fix: add tag for pre release (@next) vs release (@latest)#491lwasser wants to merge 1 commit intoall-contributors:mainfrom
lwasser wants to merge 1 commit intoall-contributors:mainfrom
Conversation
lwasser
commented
Mar 9, 2026
| workflow_dispatch: | ||
| release: | ||
| types: [published, prereleased] | ||
| types: [released, prereleased] |
lwasser
commented
Mar 9, 2026
| - name: Publish to NPM via trusted publishing (tag next if prerelease) | ||
| run: | | ||
| if [[ "${{ github.event.release.prerelease }}" == "true" ]]; then | ||
| npm publish --provenance --tag next |
Member
Author
There was a problem hiding this comment.
Only if an prerelease is created, add a tag.
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.
Phew, so the node also requires a tag when publishing a prerelease to avoid defaulting to latest, which we don't want. so this cleans up a few things
✅ The build triggers on both a release and a prerelease. (it was triggering twice previously)
✅ Then the action figures out if this is a prerelease, publish, but add the tag "next" otherwise latest
NPM is recognizing the handshake now so it's just a matter of getting the tags right (i think).
What:
Why:
How:
Checklist: