The GitHub Actions job "Release constraints" on airflow.git/v3-3-test has 
failed.
Run started by GitHub user potiuk (triggered by potiuk).

Head commit for run:
188b92cdb1bdc6c7cb016cfa1613775313b19556 / Jarek Potiuk <[email protected]>
Fail constraints generation when a released provider is downgraded (#69870) 
(#71082)

* Fail constraints generation when a released provider is downgraded

Released provider versions only ever move forward on PyPI, so a lower
provider version in freshly generated PyPI constraints than in the
already-published constraints is never intentional. It means the highest
resolution dragged an old provider back in because a broken dependency
version constrained it. Left unnoticed, such a downgrade would be
committed to the constraints branch and shipped to users.

The regular `constraints` generation now compares each released provider
against the latest published constraints and stops with an error when any
would be downgraded, so the problem surfaces in CI instead of being
published. When it happens on the canary/push builds it also posts an
alert to the CI Slack channel, since there is no PR author watching those
runs, so maintainers learn about it immediately.

* Load provider dependencies lazily in generate-constraints script

The script read the gitignored, generated generated/provider_dependencies.json
at import time. That file is not generated in the "Scripts tests" CI job, so
importing the module (which the new tests do at collection) failed with
FileNotFoundError and broke test collection. Only 
get_all_active_provider_distributions
needs the data, so load it there instead of at module import, keeping the module
importable without the generated artifact.

(cherry picked from commit 1224056f4f9f97755c889ca3e9cf76c4229fc5b9)

Report URL: https://github.com/apache/airflow/actions/runs/30900845923

With regards,
GitHub Actions via GitBox


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to