chore: configure release-please to stay on 0.x until 1.0 is explicitly cut

[DavidCozens]

Purpose

Align release-please's version-bump policy with the repo's stated release strategy: 0.x is the beta series, breaking changes during 0.x are expected, 1.0.0 is cut deliberately when the API is stable.

Today the standing release-please PR (#101) proposes 1.0.0 because the commit history contains a BREAKING CHANGE (the S3.6 TcpSender → StreamSender rename) and release-please's default pre-1.0 behaviour jumps straight to 1.0 on any ! commit. That doesn't match intent — we're not ready to commit to API stability.

Change Description

Add "bump-minor-pre-major": true to release-please-config.json. With this flag, in the 0.x series:

• feat: / feat!: / BREAKING CHANGE → 0.x → 0.(x+1) (minor bump, no jump to 1.0).
• fix: → 0.x.y → 0.x.(y+1) (patch).

After 1.0.0 is cut (whenever that happens), the flag is a no-op and normal SemVer resumes: feat!: → major, feat: → minor, fix: → patch.

Test Evidence

• JSON validated.
• No CI gate exercises this file.
• Observable effect: once this merges to main, release-please re-runs and PR chore(main): release 0.1.0 #101's title updates from chore(main): release 1.0.0 to chore(main): release 0.1.0. That's the confirmation signal.

Areas Affected

• release-please-config.json — one line added.

No code or docs touched.

Summary by CodeRabbit

• Chores
  • Updated release versioning configuration to adjust how version bumps are performed before major releases.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 55e307e0-6d7c-4b0d-9a1f-46ed7d5f4206

📥 Commits

Reviewing files that changed from the base of the PR and between eb8d90d and 539c536.

📒 Files selected for processing (1)

• release-please-config.json

---

📝 Walkthrough

Walkthrough

The pull request adds a bump-minor-pre-major: true configuration setting to the release-please configuration for the root package, modifying the release versioning behavior to perform minor version bumps prior to entering a pre-major state.

Changes

Cohort / File(s)	Summary
Release Configuration release-please-config.json	Added bump-minor-pre-major: true to the "." package configuration to enable minor version bumps before pre-major releases.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• chore: reset release versioning to 0.x #99: Also modifies release-please configuration for the project root, resetting the root manifest version to 0.0.0 alongside versioning behavior adjustments.

Poem

🐰 A tiny tweak to versioning flow,
Where minor bumps precede the show,
Before the major version springs,
Release-please now gently brings,
A smoother path to versions new! 🚀

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title directly and clearly describes the main change: configuring release-please to keep versioning in 0.x series until 1.0 is explicitly cut, which matches the changeset perfectly.
Description check	✅ Passed	The description comprehensively covers all required template sections: Purpose (why the change is needed with context), Change Description (what was changed and how), Test Evidence (validation approach and observable effect), and Areas Affected (scope of changes).
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/release-please-stay-on-0.x

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

☀️   Quality Summary

   🚦   Unit Tests (GCC): 100% successful (✔️ 775 passed, 🙈 3 skipped)
   🚦   Unit Tests (Clang): 100% successful (✔️ 727 passed, 🙈 3 skipped)
   🚦   Unit Tests (Sanitize): 100% successful (✔️ 727 passed, 🙈 3 skipped)
   🚦   Integration Tests (OpenSSL): 100% successful (✔️ 9 passed)
   🚦   BDD Tests (Linux): 100% successful (✔️ 36 passed)
   🚦   BDD Tests (Windows): 58% successful (✔️ 21 passed, 🙈 15 skipped)
   🚦   Unit Tests (MSVC): 100% successful (✔️ 600 passed, 🙈 1 skipped)
   ⚠️   Clang-Tidy: No warnings
   ⚠️   CPPCheck: No warnings

---

Created by Quality Monitor v1.14.0 (#f3859fd). More details are shown in the GitHub Checks Result.