github-actions[bot] opened a new pull request, #76597:
URL: https://github.com/apache/airflow/pull/76597

   * Let a final release override the pending-provider-candidate guard
   
   A final release-constraints run fails when a provider's newest PyPI version 
is a
   pending rc, so a release never ships constraints that silently drop its own
   provider wave (#75919). But an independent provider wave can overlap a core
   release - e.g. an accelerated release landing during a wave of breaking 
provider
   majors it was never tested against - and there the release should pin the
   currently-released providers and ship.
   
   Expose fail-on-pending-provider-candidates as an optional override on the
   release-constraints workflow. start-release asks before resolving, and the
   standalone 'breeze workflow-run release-constraints' takes the flag. Default
   behaviour is unchanged: a final still fails on a pending candidate unless 
the RM
   opts out, and the constraints never pin a release candidate either way.
   
   Co-Authored-By: Claude <[email protected]>
   
   * Simplify the override prompt and fix its tests
   
   The default (no) keeps the guard; yes pins the currently-released providers. 
Mock
   the prompt in the regenerate_constraints tests and cover both answers.
   
   Co-Authored-By: Claude <[email protected]>
   
   * Only prompt for the override when a provider candidate is actually pending
   
   Check PyPI for providers whose newest version is a pending rc, and offer the
   override only when the final constraints run would actually fail - no prompt 
on a
   normal release. Addresses review feedback. Detection reused from #76593.
   
   Co-authored-by: Amogh Desai <[email protected]>
   Co-Authored-By: Claude <[email protected]>
   
   * handling review comments
   
   ---------
   (cherry picked from commit e0b7126d57325d35ec8acaacb1a5b22b1ac0b9c4)
   
   Co-authored-by: Rahul Vats <[email protected]>
   Co-authored-by: Claude <[email protected]>
   Co-authored-by: Amogh Desai <[email protected]>
   Co-authored-by: Amogh Desai <[email protected]>


-- 
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]

Reply via email to