[v3-2-test] Bump uv floor to 0.11.8, override cooldown for uv (#66042)#66054
Merged
potiuk merged 1 commit intoapache:v3-2-testfrom Apr 28, 2026
Merged
[v3-2-test] Bump uv floor to 0.11.8, override cooldown for uv (#66042)#66054potiuk merged 1 commit intoapache:v3-2-testfrom
potiuk merged 1 commit intoapache:v3-2-testfrom
Conversation
Pins `[tool.uv] required-version` (and the matching marker-tagged constants in breeze) to 0.11.8 across the root and the three workspace members that carried their own (stale) floor (`airflow-core`, `airflow-ctl`, `dev/mypy` — all previously `>=0.6.3`). The bump picks up the timestamp-elision fix from astral-sh/uv#19022 (closes astral-sh/uv#18708 — relative `exclude-newer` no longer writes a churning timestamp into uv.lock that two branches collide on). Drops uv's per-package cooldown to "12 hours" in both [tool.uv.exclude-newer-package] and [tool.uv.pip.exclude-newer-package]; without the override the project-wide 4-day window blocks a freshly-released uv from being adopted as the floor. The override is flagged "REMOVE BY 2026-05-01" — once 0.11.8 is older than the global 4-day cooldown the override is redundant. Bumps AIRFLOW_UV_VERSION across Dockerfiles, breeze constants, and the image-args doc to match. The `# sync-uv-min-version`-tagged test fixtures were auto-rewritten by the prek hook of the same name. uv.lock confirms the upstream fix is engaged: `exclude-newer` reads as the no-op `0001-01-01T00:00:00Z` placeholder. (cherry picked from commit dbfc27d)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport of #66042 to
v3-2-test.Bumps the project's
[tool.uv] required-versionfloor from>=0.9.17to>=0.11.8to pick up the timestamp-elision fix fromastral-sh/uv#19022
(astral-sh/uv#18708) — relative
exclude-newercooldowns no longer write a churning timestamp intouv.lockthat two branches collide on.
Brings across the same set of changes as on
main: bumps the# sync-uv-min-versionmarkers in breeze, syncsAIRFLOW_UV_VERSIONacrossDockerfile/Dockerfile.ci/the breeze constants/the image-args doc, adds theuv = "12 hours"override under[tool.uv.exclude-newer-package]and[tool.uv.pip.exclude-newer-package](REMOVE BY 2026-05-01), and regeneratesuv.locksoexclude-neweris the no-op0001-01-01T00:00:00Zplaceholder.Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.7) following the guidelines