potiuk opened a new pull request, #66042:
URL: https://github.com/apache/airflow/pull/66042

   ## Summary
   
   - Bump `[tool.uv] required-version` floor `0.11.7` → `0.11.8` to pick up
     [astral-sh/uv#19022](https://github.com/astral-sh/uv/pull/19022), which
     closes [astral-sh/uv#18708](https://github.com/astral-sh/uv/issues/18708) —
     relative `exclude-newer` cooldowns no longer write a live timestamp into
     `uv.lock` that two concurrent branches collide on.
   - Override `uv = "12 hours"` in `[tool.uv.exclude-newer-package]` and
     `[tool.uv.pip.exclude-newer-package]` so the freshly-published 0.11.8 isn't
     gated by the project-wide 4-day cooldown. **Marked `REMOVE BY 2026-05-01`**
     in both call sites — once 0.11.8 is older than the global window the
     override is redundant and should be deleted.
   - Sync `AIRFLOW_UV_VERSION` across `Dockerfile`, `Dockerfile.ci`, the breeze
     constants, and the image-args doc table.
   - The two `# sync-uv-min-version`-tagged constants
     (`_PROVIDERS_DOCKER_UV_MIN_VERSION`, `_MIN_UV`) were rewritten
     automatically by the matching prek hook.
   - `uv.lock` confirms the upstream fix is engaged — `exclude-newer` reads as
     the no-op `0001-01-01T00:00:00Z` placeholder.
   
   ## Test plan
   
   - [x] Local `uv lock` succeeds with the new floor + cooldown override.
   - [x] `prek run --from-ref main --stage pre-commit` passes (incl. the
         `sync-uv-min-version-markers` hook).
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — Claude Code (Opus 4.7)
   
   Generated-by: Claude Code (Opus 4.7) following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)


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