ci(release): bump minor for breaking changes before 1.0

[magrhino]

Summary

Release Please opened #824 as chore: release 1.0.0 because the refactor(wudup)!: commits since v0.65.2 count as breaking changes and, without bump-minor-pre-major, a breaking change on 0.x bumps the major version. WUDup is not ready to leave beta, so breaking changes should bump the minor version until 1.0 is cut deliberately.

• Set bump-minor-pre-major: true for the root package in release-please-config.json. The pending release should be regenerated as 0.66.0.
• Leaving beta later should use an explicit Release-As: 1.0.0 commit footer.
• Uses a ci(release): subject so the release-please workflow runs on merge (it skips chore:/docs: pushes) and recomputes the open release PR.

Scope

• This PR has one reviewable objective
• Follow-up work, stacked PRs, or intentionally deferred changes are called out here: an edge image channel for soaking main on production before stable releases is tracked in Add an edge image channel to soak main on production before stable releases #827.

Checklist

• Tests added or updated — N/A, config-only change
• README.md or docs/ updated if install, deployment, config, or user-facing behavior changed — N/A
• docs/examples/template.env or docs/examples/webui.env.example updated if environment variables or example config changed — N/A
• Release Please/changelog impact considered; no manual CHANGELOG.md edit needed outside release prep

Test plan

• tests/run-all.sh — N/A, no code changed

• Focused test(s):

  • python3 -m json.tool release-please-config.json
  • python3 -m json.tool .release-please-manifest.json
  • git diff --check

• Docker or Compose validation, if container behavior changed: N/A

After merge, confirm #824 is retitled chore: release 0.66.0 before merging it.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates Release Please configuration so breaking changes remain on the 0.x minor-release track, causing the pending release to be recalculated as 0.66.0 while retaining an explicit mechanism for the eventual 1.0.0 release. The ci(release): commit subject also ensures the workflow reruns on merge.

File-Level Changes

Change	Details	Files
Configure pre-1.0 breaking changes to increment the minor version instead of creating a 1.0 major release.	Enable bump-minor-pre-major for the root package. Allow the pending release PR to be regenerated as 0.66.0. Preserve an explicit Release-As: 1.0.0 path for intentionally leaving beta.	release-please-config.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Advanced

Run ID: ac248478-f9fd-434b-a30a-fb510281fbad

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.

---

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.}

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud