The GitHub Actions job "uv in /. for flask - Update #1279899662" on 
airflow.git/main has failed.
Run started by GitHub user dependabot[bot] (triggered by dependabot[bot]).

Head commit for run:
489471afd09df1582108f32ba70f2e280a7c6fdd / Jarek Potiuk <[email protected]>
Switch CI dependency management from constraints to uv.lock (#63609)

* Switch CI dependency management from constraints to uv.lock

closes: #54609

* Fix selective_checks tests for push events without upgrade

Push events no longer trigger upgrade-to-newer-dependencies unless
uv.lock or pyproject.toml files changed. Updated test expectations.

* Fix remaining selective_checks tests for push events

Update two more test cases that expected upgrade-to-newer-dependencies
to be true for PUSH events.

* Fix CI failures: include uv.lock in Docker context and handle missing 
constraints

- Add uv.lock to .dockerignore allowlist so uv sync --frozen works in Docker 
builds
- Make packaging install in install_from_docker_context_files.sh conditional on
  constraints.txt existing, since the uv.lock path skips constraints download

* Fix static checks: update uv.lock and breeze docs after rebase

* Use install script with uv.lock constraints for dev dependencies in CI

Revert the entrypoint_ci.sh change from `uv sync --all-packages` back
to using the install_development_dependencies.py script. The uv sync
approach fails when provider source directories are not fully available
in the container (e.g. with selected mounts).

Instead, generate constraints from uv.lock via `uv export` and pass
them to the existing script, which installs only the needed development
dependencies via `uv pip install`.

Also add uv.lock to VOLUMES_FOR_SELECTED_MOUNTS so it is available
inside containers using the "tests and providers" mount mode.

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

With regards,
GitHub Actions via GitBox


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

Reply via email to