Bump uv to 0.5.11

[kaxil]

https://github.com/astral-sh/uv/releases/tag/0.5.11

---

^ 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 newsfragments.

[raphaelauv]

the docker image of 2.10.4 is still using uv 0.4.29

could we backport this PR on 2.10.X ? thanks all

[potiuk]

You can do it yourself. Maintainers don't do any backporting other than to latest version of latest released branch. And it's not blociking anyone to bump the UV version. Maybe you can just try to backpor it for 2.10.5 - there is no partucular need to wait for "someone else" to do it.

[raphaelauv]

hello potiuk , thanks for the answser, my question was not explicit.

about there is no partucular need to wait for "someone else" to do it.

I was aksing for guidance to apply the good process, cause I seen the doc https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#how-to-backport-pr-with-github-actions ( and many discussion on the slack contributors about backport ) and I'm not a committer, so I don't know what to do.

Thanks

[potiuk]

See https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#how-to-backport-pr-with-cherry-picker-cli

Following this process you can cherry-pick and open PR regardless if you are committer or not.