potiuk opened a new pull request, #75329: URL: https://github.com/apache/airflow/pull/75329
Betas and release candidates no longer get a `constraints-<VERSION>` branch of their own. Like finals, they commit onto the shared `constraints-X-Y` branch and are tagged `constraints-<VERSION>`. A per-candidate branch had the same name as the candidate's tag, which made `constraints-<VERSION>` ambiguous for git and for anything that resolves constraints by that name. Re-running the workflow for the same candidate now adds a commit on `constraints-X-Y` and re-creates the tag. If a leftover `constraints-<VERSION>` branch from the old layout still exists, the workflow fails and prints the command to delete it instead of silently keeping it. The release guide in `dev/README_RELEASE_AIRFLOW.md` is updated to match. Checks run locally: prek pre-commit and manual hooks on the changed files pass (yamllint, zizmor, markdownlint, etc.). The lychee link check could not run locally (no Docker access), and the workflow itself can only be exercised by a real `release-constraints` run. --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Code (Opus 5) Generated-by: Claude Code (Opus 5) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
