Add common.compat provider #40374
Merged
Add common.compat provider #40374
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
potiuk
requested review from
eladkal,
ferruzzi,
mobuchowski,
pankajkoti and
romsharon98
ferruzzi
approved these changes
Jun 21, 2024
potiuk
force-pushed
the
add-common-compat-provider
branch
from
64aac58 to
d1d3e8f
Compare
romsharon98
approved these changes
Jun 21, 2024
potiuk
force-pushed
the
add-common-compat-provider
branch
from
d1d3e8f to
090c6bd
Compare
potiuk
force-pushed
the
add-common-compat-provider
branch
from
090c6bd to
03180d6
Compare
ferruzzi
reviewed
Jun 21, 2024
96 tasks
utkarsharma2
added
the
changelog:skip
romsharon98
pushed a commit
to romsharon98/airflow
that referenced
this pull request
Jul 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
^ 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 newsfragments.