Added missing planned_removal_date for google provider deprecations#63505
Open
olegkachur-e wants to merge 1 commit intoapache:mainfrom
Open
Added missing planned_removal_date for google provider deprecations#63505olegkachur-e wants to merge 1 commit intoapache:mainfrom
olegkachur-e wants to merge 1 commit intoapache:mainfrom
Conversation
boring-cyborg
bot
added
area:logging
area:providers
provider:google
Contributor
SameerMesiah97
left a comment
SameerMesiah97
left a comment
There was a problem hiding this comment.
Can you link the issue for this? Right now, the addition of the deprecation messages seems a bit scattershot. Is there a list of methods you are adjusting the warnings for or are you just going through the provider and adding this line to all warning messages that look like deprecation notifications?
olegkachur-e
force-pushed
the
add_manual_deprecations_dates
branch
from
db30569 to
1051664
Compare
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
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.
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.