Skip to content
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

Get rid of lowest-direct resolution in no-constraint upgrades with uv #38109

Merged
merged 1 commit into from
Mar 13, 2024

Conversation

potiuk
Copy link
Member

@potiuk potiuk commented Mar 13, 2024

When we fall-back to no-constraint mode in uv, we used so far lowest-direct resolution - but it could cause a really old set of versions to be installed with some strange pyproject.toml errors (for example zenpy==2.0.32 had a buggy pyproject.toml and it caused editable local install to fail.


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

When we fall-back to no-constraint mode in uv, we used so far
lowest-direct resolution - but it could cause a really old set of
versions to be installed with some strange pyproject.toml errors
(for example zenpy==2.0.32 had a buggy pyproject.toml and it
caused editable local install to fail.
@potiuk potiuk requested a review from ashb as a code owner March 13, 2024 13:13
@boring-cyborg boring-cyborg bot added area:dev-tools area:production-image Production image improvements and fixes labels Mar 13, 2024
@potiuk
Copy link
Member Author

potiuk commented Mar 13, 2024

@potiuk
Copy link
Member Author

potiuk commented Mar 13, 2024

That failure should also be fixed by #38110, but anyhow it's likely better to keep default resolution strategy for those upgrades. --lowest-direct was actually potentially disruptive as it would potentially downgrade some of the direct dependencies. We will - in the future run --lowest resolution to test our min-dependencies and run separate tests with those, but until we do it, having default resolution is just better.

Copy link
Contributor

@amoghrajesh amoghrajesh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks. LGTM

@potiuk potiuk merged commit 71ef168 into apache:main Mar 13, 2024
95 of 100 checks passed
@potiuk potiuk deleted the get-rid-of-lowest-direct-resolution branch March 13, 2024 14:59
drajguru pushed a commit to drajguru/airflow that referenced this pull request Mar 14, 2024
…apache#38109)

When we fall-back to no-constraint mode in uv, we used so far
lowest-direct resolution - but it could cause a really old set of
versions to be installed with some strange pyproject.toml errors
(for example zenpy==2.0.32 had a buggy pyproject.toml and it
caused editable local install to fail.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:dev-tools area:production-image Production image improvements and fixes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants