vatsrahul1001 opened a new pull request, #76592: URL: https://github.com/apache/airflow/pull/76592
#75919 made a final `release-constraints` run **fail** when any provider's newest PyPI version is a pending rc — so a release never ships constraints that silently drop its own provider wave. That's right when the core release and the provider wave are the same wave. But an **independent** provider wave can overlap a core release. Concretely: 3.4.0 passed an accelerated vote while a separate provider wave (32 providers at rc1, including 11 breaking majors) is mid-vote. `start-release` → final constraints would `sys.exit(1)` on all 32 — and since `regenerate_constraints` runs *after* the irreversible PyPI upload, it would leave a half-finished GA. rc1/rc2/rc3 were all tested against the *current* provider finals, so pinning those (not the untested breaking wave) is also the more correct result here. This exposes `fail-on-pending-provider-candidates` as an **optional override**: - new workflow input on `release-constraints.yml` (empty = derive, as today); - `start-release` asks before resolving — keep the guard (default) or pin the currently-released providers and proceed; - `breeze workflow-run release-constraints --fail-on-pending-provider-candidates false` for the standalone path. **Default behaviour is unchanged** — a final still fails on a pending candidate unless the RM explicitly opts out, and the constraints never pin a release candidate either way (the override only lets the run pin each provider's newest *final* instead of stopping). README updated with the escape hatch. cc @potiuk (author of #75919) — does this shape work for you? ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude (Claude Code) Generated-by: Claude Code 🤖 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]
