release: in-memory version bump (no commit to main)#11
Merged
Conversation
- npm version runs in CI working directory only, never committed - release-it tags + publishes from the bumped package.json - branch protection is never hit - reset version to 0.1.0 as base for future bumps
package.json version on main is irrelevant — the workflow fetches the real latest from the npm registry, bumps it (patch/minor/major), and writes to package.json in the CI working directory only. Nothing is committed to main.
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
In-memory version bump — release-it never pushes commits to main, so branch protection is never hit.
How it works
npm version <patch|minor|major> --no-git-tag-versionbumpspackage.jsonin the CI working directory onlyrelease-itreads the bumped version, publishes to npm, pushes a git tag, and creates a GitHub releaseChanges
.release-it.json:commit: false,requireCleanWorkingDir: false,npm.version: false.github/workflows/release.yaml: addsnpm versionstep before release-it, keepsworkflow_dispatchwith patch/minor/major inputpackage.jsonversion reset to0.1.0as base for future bumpsTrade-off
package.jsonon main always shows the base version (0.1.0). The real version lives in npm + git tags. This is fine for a library.