Repository navigation
docs: require a version bump for every feature and fix - #28
Merged
MatiasOS merged 1 commit intoSep 14, 2026
Merged
Conversation
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
1 participant
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
Documents a versioning rule so a merged change can't silently skip publishing again, the way #26 did. The 1.8.0 bump that releases #26 is a separate PR (
chore/release-1.8.0).npm-publish.ymlpublishes on every push tomain, butJS-DevTools/npm-publishskips a version npm already has without failing the run. A PR that ships code without a bump therefore releases nothing while the workflow stays green.The rule
Every PR that adds functionality or resolves an issue bumps
package.jsonin that same PR, following semver — when a PR mixes kinds of change, the highest level wins:feat)fix,perf, behaviour-changingrefactor)The bump is its own commit with the bare version as the subject (e.g.
1.8.1), made withnpm version <level> --no-git-tag-versionsopackage-lock.jsonstays in sync. PRs that change nothing undersrc/— docs, tests, CI, tooling — are exempt.Changes
CLAUDE.md: new Versioning section after CI/CD Pipeline, a note on the publish step's silent skip, and a pointer in Important Notes for AI AssistantsREADME.md: rule added to Version Management; the Manual Release and Automated Release steps now expect the bump to arrive with the PRDocumentation only — this adds no CI enforcement.