eladkal opened a new pull request, #25799: URL: https://github.com/apache/airflow/pull/25799
Adding `RemoveInAirflow3DeprecationWarning` and `AirflowProviderDeprecationWarning` `RemoveInAirflow3DeprecationWarning` - modifying all occurrences of `DeprecationWarning` in core to the new class. `AirflowProviderDeprecationWarning` - only adding the class. We can not yet replace warnings in provider. This will be useful when minimum provider version would be on Airflow 2.4 (or the release of this PR) Closes: https://github.com/apache/airflow/issues/22356 **Todo:** [ ] Verify no missing directories [ ] fix tests of deprecation warnings [ ] We have some occurrences of `PendingDeprecationWarning` in the code base but I'm not sure if we have that distinction? Should we also have `RemoveInAirflow3PendingDeprecationWarning` ? <!-- Thank you for contributing! Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. Feel free to ping committers for the review! In case of an existing issue, reference it using one of the following: closes: #ISSUE related: #ISSUE How to write a good git commit message: http://chris.beams.io/posts/git-commit/ --> --- **^ Add meaningful description above** Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)** for more information. In case of fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed. In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). In case of backwards incompatible changes please leave a note in a newsfragment file, named `{pr_number}.significant.rst` or `{issue_number}.significant.rst`, in [newsfragments](https://github.com/apache/airflow/tree/main/newsfragments). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
