Fix deprecation warnings for workers.logGroomerSidecar#66238
Merged
jscheffl merged 1 commit intoMay 1, 2026
Conversation
Contributor
|
Was this only in 1.x line a problem? |
Contributor
Author
|
Ah, did a couple of things at once, and I took the wrong branch. Do you think that a cherry picker will work from 1.2x to main for this? 🤔 If not, I will open the same PR for the main |
1 task
Contributor
No worry, forward ported in #66243 - just via |
shahar1
pushed a commit
that referenced
this pull request
May 2, 2026
29 tasks
Contributor
|
Thank you and sorry for the additional work I caused 😅 |
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
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.
Reverts part of #66012, which introduced deprecation warning generation for non-default values, so e.g. users who are not using these options would see the deprecation warnings during chart deployment.
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.