[v3-0-test] Set minimum version for common.messaging to 1.0.3 (#54160) #54176
+4
−4
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
The apache#51774 changed the important way how intialization is done, it was causing circular imports in case it was imported directly. This PR changes minimum version of common messaging for all providers using it and generally for core airflow. (cherry picked from commit 9cc0717)
potiuk
requested review from
ashb,
eladkal,
gopidesupavan and
o-nikolas
as code owners
boring-cyborg
bot
added
area:dev-tools
area:providers
backport-to-v3-1-test
potiuk
changed the title
ashb
approved these changes
Aug 6, 2025
54 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.
The #51774 changed the important way how intialization is done, it was causing circular imports in case it was imported directly.
This PR changes minimum version of common messaging for all providers using it and generally for core airflow.
(cherry picked from commit 9cc0717)
^ 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.