Skip to content

Remove deprecated code from providers before Airflow 2.11.0 release #44559

@eladkal

Description

@eladkal

Body

Following [LAZY CONSENSUS] Remove deprecations from providers prior to Airflow 2.11 release this issue will track the progress of the removal status.

How to remove?

  1. PRs should be easy to review, You can handle more than 1 provider in the same PR but please use judgment about how many files the PR changes. Please use meaningful commit message.
  2. Find all deprecated code in a provider and accommodate for the needed change (normally the code has deprecation warning that indicates what needs to be removed). Make sure you are not removing code that was just deprecated in recent PR and was never released in stable version. Do not bulk remove!
  3. Add entry to CHANGELOG.rst with information about what was removed and how to mitigate (normally it's copy/paste with minor adjustments to the deprecation warning). Use the following blockright after the Changelog line:
main
....

.. warning::
  All deprecated classes, parameters and features have been removed from the {provider_name} provider package.
  The following breaking changes were introduced:

  * what was removed and how to mitigate

  1. If provider was already handled and introduce new deprecation do not remove again (at least not for now).

List of providers:

Maintainers please update the list with the relevant PRs/status

Committer

  • I acknowledge that I am a maintainer/committer of the Apache Airflow project.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions