mirror of
https://github.com/apache/airflow.git
synced 2026-11-04 15:19:48 +00:00
Ash Berlin-Taylor
efb49f5e36
Several hooks ran uv without --frozen, so a commit could re-lock with whichever uv was on PATH (seen: lock format revision and environment markers rewritten by an unrelated commit). Set UV_FROZEN=1 through prek's default_env (needs prek 0.4.8); the manual upgrade hooks set UV_FROZEN=0 because they need real resolution. default_env only applies to hooks in the root config, so check-provider-yaml-valid, which runs `uv sync` inside breeze against the bind-mounted host uv.lock, now passes --frozen itself. update-uv-lock ran `uv lock --frozen`, which exits 0 on a stale lock, and CI always skipped it, so the 2026-10-14 providers release merged with version bumps that were never re-locked. Run `uv lock --check` with UV_FROZEN=0 and stop skipping it in CI. The breeze shim passes --locked, which older uv rejects together with an inherited UV_FROZEN. Unset UV_FROZEN in the shim and bump SHIM_VERSION to 3 so existing installs are told to re-run setup_breeze. test_get_expected_shim_version_reads_real_setup_script asserted the exact SHIM_VERSION, so it failed on every bump without saying what broke. It now only asserts that the real setup_breeze still yields an integer version, which is what ties the parser to the real file.