Airflow 2 to 3 auto migration rules

[Lee-W]

Description

Why

As we're introducing breaking changes to the main branch, it would be better to begin recording the things we could use migration tools to help our users migrate from Ariflow 2 to 3.

The breaking changes can be found at https://github.com/apache/airflow/pulls?q=is%3Apr+label%3Aairflow3.0%3Abreaking.

Rules

• [ ] airflow.sensors.external_task.ExternalTaskSensorLink → airflow.sensors.external_task.ExternalDagLink
  • https://github.com/apache/airflow/pull/41391#issuecomment-2282938360
• [ ] airflow.models.taskMixin.TaskMixin → airflow.models.taskMixin.DependencyMixin
  • https://github.com/apache/airflow/pull/41394
• [ ] airflow.contrib.*

  • 41366

• [ ] airflow.models.ImportError -> airflow.models.errors.ParseImportError

  • 41367

• [ ] Deprecated imports from various places

  • 41368

    Related issues

No response

Are you willing to submit a PR?

• [X] Yes I am willing to submit a PR!

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[Lee-W]

The Rules now is an example of how these changes can be recorded. I will check the existing breaking changes and update the rules. It would be great if folks could help update this list if you know there are breaking changes.

[potiuk]

I pinned the issue - this way it will show up at the top of "Issues" list in the repo

[potiuk]

[Lee-W]

Thanks!

[eladkal]

We can just go over all the significant newsfragments and create a rule for them or keep some reasoning why it doesn't require one