Automate version bumping in NPM publish workflow#102
Merged
bartveneman merged 1 commit intomainfrom Mar 18, 2026
Merged
Conversation
Extract version from release tag and update package.json before publishing to NPM, then commit and push the version bump back to main.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #102 +/- ##
=======================================
Coverage 96.71% 96.71%
=======================================
Files 14 14
Lines 1064 1064
Branches 142 142
=======================================
Hits 1029 1029
Misses 34 34
Partials 1 1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Bundle ReportBundle size has no change ✅ |
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
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
Updated the NPM publish GitHub Actions workflow to automatically bump the package version during the release process, ensuring the published package version matches the git release tag.
Key Changes
contentspermission fromreadtowriteto allow pushing commitspackage.jsonImplementation Details
npm versionwith the--no-git-tag-versionflag to avoid creating duplicate git tagsgithub-actions[bot]user for the automated commitpackage.jsonandpackage-lock.jsonare committed to maintain lockfile consistencyv1.0.0→1.0.0)https://claude.ai/code/session_019neB1M5BGWawFNHeFZsyPZ