Repository navigation
ci: require a version bump on every PR - #187
Merged
Merged
Conversation
ccampbell-aai
force-pushed
the
ccampbell/version-bump-check
branch
from
September 19, 2026 23:22
0673039 to
a09e0fe
Compare
ccampbell-aai
added
the
skip-version-bump
Adds a Version Bump Check workflow that runs on every PR into main and fails unless package.json's "version" is strictly greater than the base branch's (compared with semver) and CHANGELOG.md has a matching "## [x.y.z]" entry. The skip-version-bump label bypasses it for PRs that intentionally ship no release. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
ccampbell-aai
force-pushed
the
ccampbell/version-bump-check
branch
from
September 19, 2026 23:28
a09e0fe to
37bcb4f
Compare
ccampbell-aai
marked this pull request as ready for review
September 19, 2026 23:32
aurpsis-aai
approved these changes
Sep 21, 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
mainand fails unlesspackage.json's"version"is strictly greater than the base branch's version.## [x.y.z]heading inCHANGELOG.md, since Node releases ship both files together (see anychore(release)commit).semver(pinned7.6.3vianpx,--include-prereleaseso a prerelease head still counts as a bump); unparseable versions fail with a clear error.skip-version-bumplabel (created in this repo) to a PR that intentionally ships no release (CI-only, docs-only). The trigger includeslabeled/unlabeled, so applying or removing the label re-runs the check without a new push.skip-version-bumplabel rather than a bump.Why
Publishing is release-driven off
main, so a merge without a bump means the next release either re-uses a version or needs a follow-up bump. Nothing enforced this before; #173 nearly merged without one.Follow-up after merge
Add
Version incrementedas a required status check onmainin branch protection. Until then the job is advisory only.Test plan
4.41.3== head4.41.3) — runskip-version-bump→ job skipped — run4.41.3 → 4.41.4+ CHANGELOG entry commit passes the check in CI, then reverted — run🤖 Generated with Claude Code