-
Notifications
You must be signed in to change notification settings - Fork 14.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump uv
to 0.4.22
#43056
Bump uv
to 0.4.22
#43056
Conversation
@potiuk Got another one 😆 |
This one fixes an issue @ashb raised: astral-sh/uv#8041 |
They are indeed working with lightning speed :) |
Since astral-sh/uv#7172 was added we need to add this
Sorry for the |
Thanks @charliermarsh , I appreciate the quick turnaround |
Thanks @charliermarsh and the team (as usual :) . We are now getting more and more into using |
Now that astral-sh/uv#8236 is fixed (a bug in uv 0.4.22), we can remove `--no-sources` (used in `uv pip install`) introduced in apache#43056
Now that astral-sh/uv#8236 is fixed (a bug in uv 0.4.22), we can remove `--no-sources` (used in `uv pip install`) introduced in #43056
https://pypi.org/project/uv/0.4.22 I added `--no-sources` to our `uv pip install` command, without it, it fails with following error ``` error: Failed to build: `apache-airflow @ file:///dist/apache_airflow-3.0.0.dev0.tar.gz` Caused by: Failed to parse entry for: `local-providers` Caused by: Package is not included as workspace package in `tool.uv.workspace` ``` Example: https://github.com/apache/airflow/actions/runs/11354720505/job/31582868760#step:11:2896
Now that astral-sh/uv#8236 is fixed (a bug in uv 0.4.22), we can remove `--no-sources` (used in `uv pip install`) introduced in apache#43056
https://pypi.org/project/uv/0.4.22 I added `--no-sources` to our `uv pip install` command, without it, it fails with following error ``` error: Failed to build: `apache-airflow @ file:///dist/apache_airflow-3.0.0.dev0.tar.gz` Caused by: Failed to parse entry for: `local-providers` Caused by: Package is not included as workspace package in `tool.uv.workspace` ``` Example: https://github.com/apache/airflow/actions/runs/11354720505/job/31582868760#step:11:2896
Now that astral-sh/uv#8236 is fixed (a bug in uv 0.4.22), we can remove `--no-sources` (used in `uv pip install`) introduced in apache#43056
https://pypi.org/project/uv/0.4.22 I added `--no-sources` to our `uv pip install` command, without it, it fails with following error ``` error: Failed to build: `apache-airflow @ file:///dist/apache_airflow-3.0.0.dev0.tar.gz` Caused by: Failed to parse entry for: `local-providers` Caused by: Package is not included as workspace package in `tool.uv.workspace` ``` Example: https://github.com/apache/airflow/actions/runs/11354720505/job/31582868760#step:11:2896
Now that astral-sh/uv#8236 is fixed (a bug in uv 0.4.22), we can remove `--no-sources` (used in `uv pip install`) introduced in apache#43056
https://pypi.org/project/uv/0.4.22 I added `--no-sources` to our `uv pip install` command, without it, it fails with following error ``` error: Failed to build: `apache-airflow @ file:///dist/apache_airflow-3.0.0.dev0.tar.gz` Caused by: Failed to parse entry for: `local-providers` Caused by: Package is not included as workspace package in `tool.uv.workspace` ``` Example: https://github.com/apache/airflow/actions/runs/11354720505/job/31582868760#step:11:2896
Now that astral-sh/uv#8236 is fixed (a bug in uv 0.4.22), we can remove `--no-sources` (used in `uv pip install`) introduced in apache#43056
https://pypi.org/project/uv/0.4.22
I added
--no-sources
to ouruv pip install
command, without it, it fails with following errorExample: https://github.com/apache/airflow/actions/runs/11354720505/job/31582868760#step:11:2896
^ 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.