Synchronize boto3 and sqlalchemy dependency lower-binds #57385
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
Generally, we should avoid having dependencies that are not lower-bounded, because it means that accidentally we can downgrade to a really low version. Also it's good if our deps have the same lower-binds everywhere.
potiuk
requested review from
amoghrajesh,
ashb,
bugraoz93,
eladkal,
ephraimbuddy,
gopidesupavan,
hussein-awala,
jason810496,
jedcunningham,
jscheffl,
kaxil and
vincbeck
as code owners
boring-cyborg
bot
added
area:dev-tools
area:providers
backport-to-v3-1-test
jscheffl
approved these changes
Oct 27, 2025
Member
Author
|
Random races. Merging. |
Backport failed to create: v3-1-test. View the failure log Run details
You can attempt to backport this manually by running: cherry_picker 107679d v3-1-testThis should apply the commit to the v3-1-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continue |
potiuk
added a commit
to potiuk/airflow
that referenced
this pull request
Oct 28, 2025
…pache#57385) Generally, we should avoid having dependencies that are not lower-bounded, because it means that accidentally we can downgrade to a really low version. Also it's good if our deps have the same lower-binds everywhere. (cherry picked from commit 107679d) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
potiuk
added a commit
to potiuk/airflow
that referenced
this pull request
Oct 28, 2025
…pache#57385) Generally, we should avoid having dependencies that are not lower-bounded, because it means that accidentally we can downgrade to a really low version. Also it's good if our deps have the same lower-binds everywhere. (cherry picked from commit 107679d) 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
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.
Generally, we should avoid having dependencies that are not lower-bounded, because it means that accidentally we can downgrade to a really low version. Also it's good if our deps have the same lower-binds everywhere.
^ 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.