Skip to content

chore(release): bump minor rather than major for pre-1.0 breaking changes - #25

Merged
njbrake merged 1 commit into
mainfrom
chore/bump-minor-pre-major
Aug 6, 2026
Merged

chore(release): bump minor rather than major for pre-1.0 breaking changes#25
njbrake merged 1 commit into
mainfrom
chore/bump-minor-pre-major

Conversation

@njbrake

@njbrake njbrake commented Aug 6, 2026

Copy link
Copy Markdown
Member

Note: this PR was drafted by Claude via back-and-forth with @njbrake. The reasoning and decisions are his; the prose is Claude's.

Preventive: without bump-minor-pre-major, release-please turns the first breaking-change commit in a pre-1.0 package into a 1.0.0 proposal. This SDK is pre-1.0 and the Release workflow publishes on release-PR merge, so an accidental 1.0.0 would be a stability signal that can only be yanked, not withdrawn.

otari-sdk-rust hit this for real (release-please proposed 1.0.0, corrected to 0.3.0 in mozilla-ai/otari-sdk-rust#53). Same one-line change here before it can happen.

No behaviour change today: there are no ! commits pending since the last tag, so the queued release PR keeps its current version. feat: still bumps the minor, since bump-patch-for-minor-pre-major is deliberately left unset.

Validated against the release-please config schema.

@njbrake
njbrake merged commit 9100f97 into main Aug 6, 2026
3 checks passed
@njbrake
njbrake deleted the chore/bump-minor-pre-major branch August 6, 2026 16:06
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