Automate package.json version bumping in release workflow#190
Merged
bartveneman merged 1 commit intomainfrom Mar 18, 2026
Merged
Automate package.json version bumping in release workflow#190bartveneman merged 1 commit intomainfrom
bartveneman merged 1 commit intomainfrom
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #190 +/- ##
=======================================
Coverage 95.23% 95.23%
=======================================
Files 16 16
Lines 2874 2874
Branches 806 806
=======================================
Hits 2737 2737
Misses 137 137 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Bundle ReportBundle size has no change ✅ |
bartveneman
pushed a commit
to projectwallace/format-css
that referenced
this pull request
Mar 18, 2026
Automatically update package.json and package-lock.json version whenever a GitHub release is created, using the release tag name. Uses npm version --no-git-tag-version to avoid duplicate tags. Implements projectwallace/css-parser#190
bartveneman
pushed a commit
to projectwallace/color-sorter
that referenced
this pull request
Mar 18, 2026
Extracts version from the GitHub release tag (stripping the 'v' prefix), applies it to package.json via 'npm version --no-git-tag-version', commits both package.json and package-lock.json, and pushes before building and publishing to npm. Based on projectwallace/css-parser#190
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
3 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
Updated the NPM publish workflow to automatically bump the version in
package.jsonwhen a release is created, ensuring the published package version matches the git release tag.Key Changes
package.jsonImplementation Details
github.event.release.tag_nameand thevprefix is stripped before applying to npm version commandnpm versionwith--no-git-tag-versionflag to update version without creating duplicate git tagspackage.jsonandpackage-lock.jsonto maintain lockfile consistencyhttps://claude.ai/code/session_01CAvVi3i1zrJrf1B7KsRj8o