git-cliff defaults to breaking_always_bump_major = true, so a breaking change on 0.x proposed 1.0.0. This adds [bump] breaking_always_bump_major = false to keep 0.x breaking changes on the minor version. Verified locally with git-cliff 2.14.1 (the shared Release workflow's version): --bumped-version now gives v0.5.0 instead of v1.0.0 for the pending feat! (release-prep PR #179).
git-cliff defaults to `breaking_always_bump_major = true`, so a breaking change on 0.x proposed **1.0.0**. This adds `[bump] breaking_always_bump_major = false` to keep 0.x breaking changes on the minor version. Verified locally with git-cliff 2.14.1 (the shared Release workflow's version): `--bumped-version` now gives v0.5.0 instead of v1.0.0 for the pending `feat!` (release-prep PR #179).
Config-only change, no expert review.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_01SV1epy2pKvBx3yDfhxATk2
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
git-cliff defaults to
breaking_always_bump_major = true, so a breaking change on 0.x proposed 1.0.0. This adds[bump] breaking_always_bump_major = falseto keep 0.x breaking changes on the minor version. Verified locally with git-cliff 2.14.1 (the shared Release workflow's version):--bumped-versionnow gives v0.5.0 instead of v1.0.0 for the pendingfeat!(release-prep PR #179).Config-only change, no expert review.
🤖 Generated with Claude Code
https://claude.ai/code/session_01SV1epy2pKvBx3yDfhxATk2
Coverage Report
Total coverage: 21%