chore: automate npm publishing with changesets/action#1171
Merged
bryzettler merged 2 commits intodevelopfrom Apr 6, 2026
Merged
chore: automate npm publishing with changesets/action#1171bryzettler merged 2 commits intodevelopfrom
bryzettler merged 2 commits intodevelopfrom
Conversation
ChewingGlass
approved these changes
Apr 6, 2026
Replace v* tag trigger with changesets/action on develop. CI now auto-opens a Version Packages PR and publishes on merge with per-package git tags.
bryzettler
force-pushed
the
feat/workflow-dispatch-publish
branch
from
4e4dd85 to
a783137
Compare
bryzettler
changed the title
ChewingGlass
approved these changes
Apr 6, 2026
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.
Summary
v*tag trigger on the NPM Publish workflow withchangesets/actiontriggered on push todeveloppackage.jsonversions and updates CHANGELOGs@helium/blockchain-api@0.11.17)Why
The previous
v*tag convention was confusing — the tag version was arbitrary and didn't correspond to any actual package version. Changesets manages per-package versions, so a single repo-wide version tag was meaningless. There was also no record of what was published since version bumps were never committed back to the repo.New publishing flow
pnpm changeset— create a changeset alongside code changesdevelop