ci(release): keep 0.x bumps pre-major

[bradfair]

Summary

• Open release-please PR bumped to 1.0.0 because of refactor(connector)! in connector!: dialect + auth-mode subcommand tree (Postgres) #15 — ! = breaking, default behavior jumps to major.
• Not ready for v1. Enable bump-minor-pre-major + bump-patch-for-minor-pre-major so breaking on 0.x bumps minor (0.3.0) and feat bumps patch.
• After merge, release-please will recompute and replace the existing 1.0.0 PR with a 0.3.0 one.

Summary by CodeRabbit

• Chores
  • Updated release configuration settings for improved version management.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 7a49fb92-04f7-4b1e-b973-9046588620b0

📥 Commits

Reviewing files that changed from the base of the PR and between f739b38 and 511bcb1.

📒 Files selected for processing (1)

• release-please-config.json

---

📝 Walkthrough

Walkthrough

Updated release-please-config.json to enable two version-bumping configuration flags (bump-minor-pre-major and bump-patch-for-minor-pre-major) for the ana-cli package, controlling how version numbers increment during pre-major releases.

Changes

Cohort / File(s)	Summary
Release Configuration release-please-config.json	Enabled bump-minor-pre-major and bump-patch-for-minor-pre-major flags to control version-bumping behavior during pre-major release cycles.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 Whiskers twitch at config so fine,
Version numbers dance in divine line,
Minor bumps and patches align,
Pre-major releases will surely shine! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'ci(release): keep 0.x bumps pre-major' clearly and specifically describes the main change—configuring release-please to maintain pre-major versioning behavior during 0.x releases.
Description check	✅ Passed	The description provides clear context about why the configuration change is needed, referencing the breaking change commit and explaining the desired versioning behavior, though it deviates from the template structure.
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 fix/release-please-pre-major-minor

---

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