Dev-iL commented on PR #74696: URL: https://github.com/apache/airflow/pull/74696#issuecomment-6261575966
Picking up the two items from the review body — and apologies for taking a pass at the inline ones first and leaving these. **`uv.lock` revision** — fixed, it is back to `revision = 5`. One correction on the method, though: the pinned version cannot produce it. `UV_VERSION` / `AIRFLOW_UV_VERSION` is `0.12.18`, and that writes `revision = 3`; `0.13.1` writes `5`, with byte-identical content otherwise. So `uvx --from uv==0.12.18 uv lock` reproduces exactly the downgrade you flagged. I regenerated with 0.13.1 instead, so the lock now matches `main`. That leaves the pin unable to round-trip `main`'s own lockfile, which is why the line keeps flip-flopping rather than being any one contributor's slip: ``` 98391ff597 2026-10-14 3 -> 5 0f06fca0fc 2026-10-12 5 -> 3 57ad5d3053 2026-10-08 3 -> 5 ``` Either bumping `UV_VERSION` to a 0.13.x or normalising the lock back to revision 3 would stop it. Happy to open that as a separate PR — it affects every provider PR, not just this one. (It also only bites when the lock actually changes: `uv lock` leaves the file alone when nothing needs rewriting, which is what makes it look intermittent.) **Changelog** — added. I put it as a `.. note::` directly under the `Changelog` header rather than under a version heading, following #74858, #73419 and #72057, so it doesn't have to guess the next version number. I checked that `_find_insertion_index_for_version` still returns `append=True` for `3.10.1` with the note in place, so the release tooling is unaffected. Vespa's equivalent is in #75062, which this PR is now split from. **Green 3.14 provider run** — running locally now; I'll post the result. Worth noting this PR's own CI should produce it too: with the provider no longer in `excluded-python-versions`, the 3.14 provider test job now covers Cassandra, so the run on this head is the same evidence from CI rather than my laptop. --- Drafted-by: Claude Code (Opus 5) (no human review before posting) -- 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]
