Add release workflow with npm trusted publishing#3
Merged
Conversation
brunolemos
requested changes
May 23, 2026
Member
brunolemos
left a comment
brunolemos
left a comment
There was a problem hiding this comment.
Please use node 24 (LTS) in any new code
brunolemos
approved these changes
May 23, 2026
Mirrors the elements publish flow: PR merged to main triggers build & test, then a reviewer approves the publish via the npm-publish environment gate. Version is read from npm and bumped from there (patch by default, override with release:minor or release:major PR labels). Auth uses OIDC trusted publishing — no NPM_TOKEN. Also bumps ci.yml + package.json engines to Node 24 (LTS) and pnpm 10 to match the publish workflow.
ivoIturrieta
force-pushed
the
feat/publish-workflow
branch
from
5ca7ddb to
1f7b969
Compare
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
2 participants
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.
Mirrors the elements publish flow: PR merged to main triggers build & test, then a reviewer approves the publish via the npm-publish environment gate. Version is read from npm and bumped from there (patch by default, override with release:minor or release:major PR labels). Auth uses OIDC trusted publishing — no NPM_TOKEN.
Also corrects package.json version from 1.0.0 to 0.1.0 to match what is actually published on npm.