Add new publishing workflow - #53
Open
ibesora wants to merge 1 commit into
Open
Conversation
ibesora
requested review from
Xdudu and
mourner
and removed request for
Xdudu
September 4, 2026 14:19
Contributor
Author
|
@mourner I followed what you did in mapbox/polylabel#128. |
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.
Adds a minimal GitHub Actions workflow for publishing on NPM via Trusted Publishing
Configuring the environment:
GitHub repo settings → Environments → New environment → npm-release
Deployment branches and tags -> Selected branches and tags → Add rule → Ref type: Tag ->
v*Releasing with this workflow:
npm version <major|minor|patch>Get the PR green, approved and merged.
Once everything looks good,
git push --tagsto release.