Skip to content

chore: let feat commits bump the minor version pre-1.0#152

Merged
ThomasK33 merged 1 commit into
mainfrom
release-please-ts2r
Jun 12, 2026
Merged

chore: let feat commits bump the minor version pre-1.0#152
ThomasK33 merged 1 commit into
mainfrom
release-please-ts2r

Conversation

@ThomasK33

Copy link
Copy Markdown
Member

What

Removes bump-patch-for-minor-pre-major from release-please-config.json so that, while the version is below 1.0.0:

Commit Before After
feat!: / BREAKING CHANGE: 0.5.0 0.5.0
feat: 0.4.4 0.5.0
fix: 0.4.4 0.4.4

bump-minor-pre-major is kept, so breaking changes still bump the minor version instead of jumping to 1.0.0. Reaching 1.0.0 remains an explicit decision via a Release-As: 1.0.0 commit footer.

Why

Features should be visible as minor bumps (0.5.0) rather than being flattened into patch releases, while still keeping the version from crossing into 1.0.0 automatically.

Validation

  • release-please-config.json parses as valid JSON (node -e "JSON.parse(...)")
  • Config-only change; no code paths affected.

Generated with mux • Model: anthropic:claude-fable-5 • Thinking: xhigh

Drop bump-patch-for-minor-pre-major so a feat commit bumps 0.4.3 to
0.5.0 instead of 0.4.4. Breaking changes still bump the minor (not
major) via bump-minor-pre-major while the version is below 1.0.0.
@ThomasK33 ThomasK33 merged commit 6c6fa6a into main Jun 12, 2026
11 checks passed
@ThomasK33 ThomasK33 deleted the release-please-ts2r branch June 12, 2026 20:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant