Fixing uv upgrade failures on main

[amoghrajesh]

Example failures: https://github.com/apache/airflow/actions/runs/16313332961/job/46073409143

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[github-actions]

Backport failed to create: v3-0-test. View the failure log Run details

Status	Branch	Result
❌	v3-0-test

You can attempt to backport this manually by running:

cherry_picker 6aeee15 v3-0-test

This should apply the commit to the v3-0-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

[potiuk]

BTW. The title is slightly wrong: It was more of a "node version upgrade" failure - uv upgrades do not fail in "canary" builds - that would be far too frequent occurence so we make it not fail in canary :). But when you upgrade with pre-commit because of node or Python or pre-commit fail, uv will be upgraded together with them automatically.

[gopidesupavan]

BTW. The title is slightly wrong: It was more of a "node version upgrade" failure - uv upgrades do not fail in "canary" builds - that would be far too frequent occurence so we make it not fail in canary :). But when you upgrade with pre-commit because of node or Python or pre-commit fail, uv will be upgraded together with them automatically.

oo okay

[potiuk]

Cherry-picked it here #53451