Adds a callable workflow to automate the creation of hotfix branches, RTD versions, and redirects: ## Behavior - Major versions: - creates a hotfix branch - activates the branch's RTD version with slug `<major>` - sets new version as the project default - redirects `<major>.0` and `<major>.0.0` to `<major>` - Minor versions: - creates a hotfix branch - deactivates the previous minor version after changing its slug to `<major>.<minor>` (to free up the `<major>` slug) - activates the new hotfix branch's RTD version with slug `<major>` - sets new version as the project default - redirects `<major>.<minor>` and `<major>.<minor>.0` to `<major>` - Patch versions: - redirects `<major>.<minor>.<patch>` to `<major>` ## Validation I tested every case manually on my fork of Snapcraft. [These tags](https://github.com/jahn-junior/snapcraft/releases), pushed one by one, resulted in [this RTD project](https://app.readthedocs.com/projects/canonical-ecoldi-test/)'s active versions and redirects without any manual intervention. ## AI disclosure A good chunk of this workflow was implemented by Claude Sonnet 5, with lots of guidance on how the steps and API calls should look. I wrote this PR description myself though ;) --- - [X] I've followed the [contribution guidelines](https://github.com/canonical/starbase/blob/main/CONTRIBUTING.md). - [X] I've signed the [CLA](http://www.ubuntu.com/legal/contributors/). - [x] I've successfully run `make lint && make test`. - [ ] I've added or updated any relevant documentation. - [ ] In documents I changed, I [added a meta description](https://canonical-starflow.readthedocs-hosted.com/how-to/add-a-page-meta-description/) if one was missing. - [ ] I've updated the relevant release notes.