potiuk opened a new pull request, #69457: URL: https://github.com/apache/airflow/pull/69457
Constraints in the `constraints-*` branches only refresh automatically when `uv.lock` changes on a stable branch. After a providers release there is no such push, so refreshing constraints — for example to pick up newly released providers before promoting an RC — required running the breeze constraint-generation commands locally. This adds a `workflow_dispatch` trigger to the `Update constraints` workflow. The manual run is launched from `main` and takes a `ref` input (branch, tag or commit hash) selecting the sources to refresh constraints from; the target `constraints-X-Y` branch is derived automatically from that ref's `branch_defaults.py`. Running from `main` avoids cherry-picking the workflow onto `vX-Y-test` / `vX-Y-stable`, which matters because those branches diverge while RCs are being voted on. A toggle re-resolves to the newest matching dependencies from PyPI (default on). The ref is threaded through the reusable `ci-image-build` and `generate-constraints` workflows via a new optional `checkout-ref` input (backward compatible — empty keeps the current checkout behaviour for all existing callers). Because the RC constraints are frozen when the RC is cut, `breeze release-management start-release` now asks whether to base the final `constraints-<version>` tag on the latest `constraints-X-Y` branch tip (when constraints were refreshed after the last RC) instead of the RC tag. The manual procedure and the release-guide note are documented accordingly. --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Code (Opus 4.8) Generated-by: Claude Code (Opus 4.8) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) -- 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]
