Fix constraint mode when installing from dist or version airflow#60304
Merged
potiuk merged 1 commit intoapache:mainfrom Jan 9, 2026
Merged
Conversation
potiuk
requested review from
amoghrajesh,
ashb,
bugraoz93,
gopidesupavan,
jason810496,
jscheffl and
kaxil
as code owners
boring-cyborg
bot
added
area:dev-tools
backport-to-v3-1-test
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.
potiuk
force-pushed
the
force-pypi-constraints-when-installing-from-dist-or-version
branch
from
64f60ef to
097ca09
Compare
jscheffl
approved these changes
Jan 8, 2026
Contributor
jscheffl
left a comment
jscheffl
left a comment
There was a problem hiding this comment.
Cool, faster than I was able to research if configurable or if I was too stupid :-D
Member
Author
Explanation in the devlist :) |
Contributor
Unable to see and read all in parallel - I am always impressed how much content sprinkles out of your hands per hour. Hard to follow all threads and in this speed not able to contribute in parallel :-D |
potiuk
deleted the
force-pypi-constraints-when-installing-from-dist-or-version
branch
github-actions bot
pushed a commit
that referenced
this pull request
Jan 9, 2026
…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>
Backport successfully created: v3-1-test
|
potiuk
added a commit
that referenced
this pull request
Jan 9, 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>
stegololz
pushed a commit
to stegololz/airflow
that referenced
this pull request
Jan 9, 2026
…che#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.
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>
jhgoebbert
pushed a commit
to jhgoebbert/airflow_Owen-CH-Leung
that referenced
this pull request
Feb 8, 2026
…che#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.
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
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.
^ 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.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.