ci: keep release-please pre-1.0 (bump-minor-pre-major)

[amondnet]

release-please proposed 1.0.0 for the Phase 1 scaffold (release PR #2) because the config had no pre-major bump flag — a feat on 0.x defaults to 1.0.0.

Add "bump-minor-pre-major": true so features bump the minor while the major is 0. After this merges, release-please re-runs and updates PR #2 from 1.0.0 → 0.1.0; breaking changes stay in 0.x until we intentionally cut 1.0.0.

No code change — release automation config only.

---

Summary by cubic

Keep release-please in pre-1.0 mode by adding bump-minor-pre-major: true, so feat on 0.x bumps the minor instead of jumping to 1.0.0. This shifts the next release from 1.0.0 to 0.1.0 and keeps breaking changes in 0.x until we choose 1.0.0.

^{Written for commit 15b4b98. Summary will update on new commits.}

[greptile-apps]

Greptile Summary

Configures release-please to preserve pre-1.0 semantic versioning.

• Enables minor-version bumps for feature releases while the package major version remains zero.
• Keeps version synchronization with deno.json unchanged.

Confidence Score: 5/5

The PR appears safe to merge, with no actionable defects identified in the release configuration change.

The change is narrowly scoped to enabling release-please’s pre-major minor-bump behavior and does not alter application code or unrelated release settings.

Important Files Changed

Filename	Overview
release-please-config.json	Adds the package-level bump-minor-pre-major setting to keep feature releases on the 0.x version line.

_{Reviews (1): Last reviewed commit: "ci: keep release-please pre-1.0 (bump-mi..." | Re-trigger Greptile}