Repository navigation
Remove from deprecations_ignore.yml already resolved warnings exclusions - #39369
Merged
Taragolis merged 1 commit intoMay 2, 2024
Merged
Conversation
Taragolis
added
changelog:skip
Taragolis
force-pushed
the
remove-resolved-deprecations-warnings
branch
from
May 2, 2024 12:31
c280e41 to
1e2f9c1
Compare
Taragolis
requested review from
Lee-W,
dstandish,
eladkal,
hussein-awala,
jedcunningham,
uranusjr and
vincbeck
May 2, 2024 15:07
Taragolis
commented
May 2, 2024
Taragolis
marked this pull request as ready for review
May 2, 2024 15:08
vincbeck
approved these changes
May 2, 2024
hussein-awala
approved these changes
May 2, 2024
eladkal
approved these changes
May 2, 2024
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
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.
related: #38642
Some of the warnings already resolve, no reason to keep it in exclusion lists
^ 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.