prepare v1.10.3

[wollomatic]

I'm testing a (hopefully) better branching model, so that future releases are built from their release branches, not directly from the main branch.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch main

---

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

[amanda-wee]

So the plan is to merge feature and bugfix branches directly to main, and then you'll prepare a release branch for each release?

[wollomatic]

@amanda-wee Yes, exactly - similar to how Traefik handles it. A develop branch doesn’t add much value in our case (in my opinion), but release branches make it easier to manage if we ever need to support multiple versions simultaneously in the future.