-
Notifications
You must be signed in to change notification settings - Fork 16.3k
Bump min versions of crucial providers #50076
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
Merged
Merged
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
Member
Author
|
Also extracted from #50057 |
vincbeck
approved these changes
May 1, 2025
071c87d to
6abaf7f
Compare
Member
Author
|
I made a clearly visible that some of the min provider versions are overridden rather than calculated by cut-off date. |
6abaf7f to
62e1465
Compare
gopidesupavan
approved these changes
May 1, 2025
There are a few min-versions of providers that should make its way into apache-airflow pyproject.toml - because they contain crucial Airflow 3 fixes and users should not be installng those providers in lower versions. This PR adds such limits and makes it clearer when updates happen what happens and where to override them.
62e1465 to
107e6a0
Compare
Member
Author
|
I am glad I added unit tests for version update - turned out I needed to handle the comment case when changing the suffix :) |
github-actions bot
pushed a commit
that referenced
this pull request
May 1, 2025
There are a few min-versions of providers that should make its way into apache-airflow pyproject.toml - because they contain crucial Airflow 3 fixes and users should not be installng those providers in lower versions. This PR adds such limits and makes it clearer when updates happen what happens and where to override them. (cherry picked from commit e875622) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
potiuk
added a commit
that referenced
this pull request
May 1, 2025
There are a few min-versions of providers that should make its way into apache-airflow pyproject.toml - because they contain crucial Airflow 3 fixes and users should not be installng those providers in lower versions. This PR adds such limits and makes it clearer when updates happen what happens and where to override them. (cherry picked from commit e875622) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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.
There are a few min-versions of providers that should make its way into apache-airflow pyproject.toml - because they contain crucial Airflow 3 fixes and users should not be installng those providers in lower versions.
This PR adds such limits and makes it clearer when updates happen what happens and where to override them.
^ 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.