chore(release): bump the minor version for breaking changes before 1.0

[alukach]

Release-please would cut the pending release (#153) as 1.0.0 because #146 is a breaking change (feat(sts)!). We aren't ready to call this 1.0, so this sets bump-minor-pre-major: true: while the version is below 1.0, a breaking change bumps the minor version instead of the major. After this merges, release-please regenerates #153 as 0.8.0, and later breaking changes before 1.0 follow the same rule. Going to 1.0 later takes a Release-As: 1.0.0 commit footer or removing this option.

The version comes from the commits on main, not from the release PR, so a commit to #153's branch would be overwritten when release-please regenerates it.

Testing

Not run: release-please only acts on main. After merging, check that #153's title reads chore(main): release 0.8.0.

🤖 Generated with Claude Code

[claude]

Claude finished @alukach's task in 7s —— View job

---

✅ No blocking issues — safe to merge.

release-please-config.json:5 adds "bump-minor-pre-major": true at the package level, which is a valid release-please option. Under 1.0, a breaking change now bumps the minor version. The current version isn't 0.x-stale, so #153 should regenerate as 0.8.0, as the PR description says. Nothing else changed.

One note, not blocking: bump-minor-pre-major only affects breaking changes. Without bump-patch-for-minor-pre-major, a feat: commit before 1.0 also bumps the minor version, which is probably what you want.

---

💰 Estimated review cost: $0.09 · 0m06s · 4 turns

[github-actions]

🚀 Latest commit deployed to https://multistore-proxy-pr-161.development-seed.workers.dev

• Date: 2026-10-01T16:30:33Z
• Commit: 3aa936e