[v3-1-test] Fix constraint mode when installing from dist or version airflow (#60304) #60305
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…airflow (#60304) When Airflow is installed in breeze with `--use-airflow-version` and it's either wheel, dist or version number, we should use PyPI constraints, rather than source constraints, because in some edge cases, pre-installed providers might be installed using different version than the version specified in PyPI constraints. This might happen if the dependency resolution run by uv will determine that another package is more important to be installed in higher version and that higher version conflicts with newer preinstalled provider version. In this case Fab Provider is pinned with fab provider and the version of fab provider in v3-1-test sources was pretty old. (cherry picked from commit e0c5458) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
boring-cyborg
bot
added
area:dev-tools
backport-to-v3-1-test
potiuk
requested review from
amoghrajesh,
ashb,
bugraoz93,
eladkal,
gopidesupavan,
jason810496,
jscheffl,
kaxil and
potiuk
as code owners
ephraimbuddy
pushed a commit
that referenced
this pull request
Jan 13, 2026
…airflow (#60304) (#60305) When Airflow is installed in breeze with `--use-airflow-version` and it's either wheel, dist or version number, we should use PyPI constraints, rather than source constraints, because in some edge cases, pre-installed providers might be installed using different version than the version specified in PyPI constraints. This might happen if the dependency resolution run by uv will determine that another package is more important to be installed in higher version and that higher version conflicts with newer preinstalled provider version. In this case Fab Provider is pinned with fab provider and the version of fab provider in v3-1-test sources was pretty old. (cherry picked from commit e0c5458) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
ephraimbuddy
pushed a commit
that referenced
this pull request
Jan 14, 2026
…airflow (#60304) (#60305) When Airflow is installed in breeze with `--use-airflow-version` and it's either wheel, dist or version number, we should use PyPI constraints, rather than source constraints, because in some edge cases, pre-installed providers might be installed using different version than the version specified in PyPI constraints. This might happen if the dependency resolution run by uv will determine that another package is more important to be installed in higher version and that higher version conflicts with newer preinstalled provider version. In this case Fab Provider is pinned with fab provider and the version of fab provider in v3-1-test sources was pretty old. (cherry picked from commit e0c5458) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
ephraimbuddy
pushed a commit
that referenced
this pull request
Jan 16, 2026
…airflow (#60304) (#60305) When Airflow is installed in breeze with `--use-airflow-version` and it's either wheel, dist or version number, we should use PyPI constraints, rather than source constraints, because in some edge cases, pre-installed providers might be installed using different version than the version specified in PyPI constraints. This might happen if the dependency resolution run by uv will determine that another package is more important to be installed in higher version and that higher version conflicts with newer preinstalled provider version. In this case Fab Provider is pinned with fab provider and the version of fab provider in v3-1-test sources was pretty old. (cherry picked from commit e0c5458) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
85 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When Airflow is installed in breeze with
--use-airflow-versionand it's either wheel, dist or version number, we should use
PyPI constraints, rather than source constraints, because in some
edge cases, pre-installed providers might be installed using
different version than the version specified in PyPI constraints.
This might happen if the dependency resolution run by uv will
determine that another package is more important to be installed
in higher version and that higher version conflicts with newer
preinstalled provider version.
In this case Fab Provider is pinned with fab provider and the
version of fab provider in v3-1-test sources was pretty old.
(cherry picked from commit e0c5458)
Co-authored-by: Jarek Potiuk jarek@potiuk.com