-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Fix circular import when using XComObjectStorageBackend
#55805
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
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
Remove ``BaseOperator`` import from ``version_compat.py`` to prevent circular import during ``XCom`` backend resolution. The import was causing startup failures for scheduler and triggerer when XComObjectStorageBackend was configured as the XCom backend. Move ``BaseOperator`` import directly to `file_transfer.py` where it's needed, maintaining compatibility with both Airflow 2.x and 3.x while avoiding the circular dependency chain that was introduced in PR apache#52443. For use with Airflow 2.x, this is what was causing Circular import: ``` XCom Backend Resolution ↓ airflow.providers.common.io.xcom.backend ↓ airflow.providers.common.io.version_compat (imports BaseOperator at module level) ↓ airflow.models.BaseOperator (or airflow.sdk.BaseOperator) ↓ airflow.models.mappedoperator (BaseOperator imports this) ↓ airflow.triggers.base (MappedOperator imports this) ↓ airflow.models.taskinstance (triggers.base imports SimpleTaskInstance) ↓ airflow.models.xcom (TaskInstance imports XCom) ↓ resolve_xcom_backend() (tries to load XCom backend again) ↓ CIRCULAR IMPORT! 🔄 ``` Fixes apache#55803
ashb
approved these changes
Sep 17, 2025
amoghrajesh
reviewed
Sep 18, 2025
Contributor
amoghrajesh
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Damn!
78 tasks
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Sep 30, 2025
…5805) Remove ``BaseOperator`` import from ``version_compat.py`` to prevent circular import during ``XCom`` backend resolution. The import was causing startup failures for scheduler and triggerer when XComObjectStorageBackend was configured as the XCom backend. Move ``BaseOperator`` import directly to `file_transfer.py` where it's needed, maintaining compatibility with both Airflow 2.x and 3.x while avoiding the circular dependency chain that was introduced in PR apache#52443. For use with Airflow 2.x, this is what was causing Circular import: ``` XCom Backend Resolution ↓ airflow.providers.common.io.xcom.backend ↓ airflow.providers.common.io.version_compat (imports BaseOperator at module level) ↓ airflow.models.BaseOperator (or airflow.sdk.BaseOperator) ↓ airflow.models.mappedoperator (BaseOperator imports this) ↓ airflow.triggers.base (MappedOperator imports this) ↓ airflow.models.taskinstance (triggers.base imports SimpleTaskInstance) ↓ airflow.models.xcom (TaskInstance imports XCom) ↓ resolve_xcom_backend() (tries to load XCom backend again) ↓ CIRCULAR IMPORT! 🔄 ``` Fixes apache#55803
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 1, 2025
…5805) Remove ``BaseOperator`` import from ``version_compat.py`` to prevent circular import during ``XCom`` backend resolution. The import was causing startup failures for scheduler and triggerer when XComObjectStorageBackend was configured as the XCom backend. Move ``BaseOperator`` import directly to `file_transfer.py` where it's needed, maintaining compatibility with both Airflow 2.x and 3.x while avoiding the circular dependency chain that was introduced in PR apache#52443. For use with Airflow 2.x, this is what was causing Circular import: ``` XCom Backend Resolution ↓ airflow.providers.common.io.xcom.backend ↓ airflow.providers.common.io.version_compat (imports BaseOperator at module level) ↓ airflow.models.BaseOperator (or airflow.sdk.BaseOperator) ↓ airflow.models.mappedoperator (BaseOperator imports this) ↓ airflow.triggers.base (MappedOperator imports this) ↓ airflow.models.taskinstance (triggers.base imports SimpleTaskInstance) ↓ airflow.models.xcom (TaskInstance imports XCom) ↓ resolve_xcom_backend() (tries to load XCom backend again) ↓ CIRCULAR IMPORT! 🔄 ``` Fixes apache#55803
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 2, 2025
…5805) Remove ``BaseOperator`` import from ``version_compat.py`` to prevent circular import during ``XCom`` backend resolution. The import was causing startup failures for scheduler and triggerer when XComObjectStorageBackend was configured as the XCom backend. Move ``BaseOperator`` import directly to `file_transfer.py` where it's needed, maintaining compatibility with both Airflow 2.x and 3.x while avoiding the circular dependency chain that was introduced in PR apache#52443. For use with Airflow 2.x, this is what was causing Circular import: ``` XCom Backend Resolution ↓ airflow.providers.common.io.xcom.backend ↓ airflow.providers.common.io.version_compat (imports BaseOperator at module level) ↓ airflow.models.BaseOperator (or airflow.sdk.BaseOperator) ↓ airflow.models.mappedoperator (BaseOperator imports this) ↓ airflow.triggers.base (MappedOperator imports this) ↓ airflow.models.taskinstance (triggers.base imports SimpleTaskInstance) ↓ airflow.models.xcom (TaskInstance imports XCom) ↓ resolve_xcom_backend() (tries to load XCom backend again) ↓ CIRCULAR IMPORT! 🔄 ``` Fixes apache#55803
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 3, 2025
…5805) Remove ``BaseOperator`` import from ``version_compat.py`` to prevent circular import during ``XCom`` backend resolution. The import was causing startup failures for scheduler and triggerer when XComObjectStorageBackend was configured as the XCom backend. Move ``BaseOperator`` import directly to `file_transfer.py` where it's needed, maintaining compatibility with both Airflow 2.x and 3.x while avoiding the circular dependency chain that was introduced in PR apache#52443. For use with Airflow 2.x, this is what was causing Circular import: ``` XCom Backend Resolution ↓ airflow.providers.common.io.xcom.backend ↓ airflow.providers.common.io.version_compat (imports BaseOperator at module level) ↓ airflow.models.BaseOperator (or airflow.sdk.BaseOperator) ↓ airflow.models.mappedoperator (BaseOperator imports this) ↓ airflow.triggers.base (MappedOperator imports this) ↓ airflow.models.taskinstance (triggers.base imports SimpleTaskInstance) ↓ airflow.models.xcom (TaskInstance imports XCom) ↓ resolve_xcom_backend() (tries to load XCom backend again) ↓ CIRCULAR IMPORT! 🔄 ``` Fixes apache#55803
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 4, 2025
…5805) Remove ``BaseOperator`` import from ``version_compat.py`` to prevent circular import during ``XCom`` backend resolution. The import was causing startup failures for scheduler and triggerer when XComObjectStorageBackend was configured as the XCom backend. Move ``BaseOperator`` import directly to `file_transfer.py` where it's needed, maintaining compatibility with both Airflow 2.x and 3.x while avoiding the circular dependency chain that was introduced in PR apache#52443. For use with Airflow 2.x, this is what was causing Circular import: ``` XCom Backend Resolution ↓ airflow.providers.common.io.xcom.backend ↓ airflow.providers.common.io.version_compat (imports BaseOperator at module level) ↓ airflow.models.BaseOperator (or airflow.sdk.BaseOperator) ↓ airflow.models.mappedoperator (BaseOperator imports this) ↓ airflow.triggers.base (MappedOperator imports this) ↓ airflow.models.taskinstance (triggers.base imports SimpleTaskInstance) ↓ airflow.models.xcom (TaskInstance imports XCom) ↓ resolve_xcom_backend() (tries to load XCom backend again) ↓ CIRCULAR IMPORT! 🔄 ``` Fixes apache#55803
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 5, 2025
…5805) Remove ``BaseOperator`` import from ``version_compat.py`` to prevent circular import during ``XCom`` backend resolution. The import was causing startup failures for scheduler and triggerer when XComObjectStorageBackend was configured as the XCom backend. Move ``BaseOperator`` import directly to `file_transfer.py` where it's needed, maintaining compatibility with both Airflow 2.x and 3.x while avoiding the circular dependency chain that was introduced in PR apache#52443. For use with Airflow 2.x, this is what was causing Circular import: ``` XCom Backend Resolution ↓ airflow.providers.common.io.xcom.backend ↓ airflow.providers.common.io.version_compat (imports BaseOperator at module level) ↓ airflow.models.BaseOperator (or airflow.sdk.BaseOperator) ↓ airflow.models.mappedoperator (BaseOperator imports this) ↓ airflow.triggers.base (MappedOperator imports this) ↓ airflow.models.taskinstance (triggers.base imports SimpleTaskInstance) ↓ airflow.models.xcom (TaskInstance imports XCom) ↓ resolve_xcom_backend() (tries to load XCom backend again) ↓ CIRCULAR IMPORT! 🔄 ``` Fixes apache#55803
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 5, 2025
…5805) Remove ``BaseOperator`` import from ``version_compat.py`` to prevent circular import during ``XCom`` backend resolution. The import was causing startup failures for scheduler and triggerer when XComObjectStorageBackend was configured as the XCom backend. Move ``BaseOperator`` import directly to `file_transfer.py` where it's needed, maintaining compatibility with both Airflow 2.x and 3.x while avoiding the circular dependency chain that was introduced in PR apache#52443. For use with Airflow 2.x, this is what was causing Circular import: ``` XCom Backend Resolution ↓ airflow.providers.common.io.xcom.backend ↓ airflow.providers.common.io.version_compat (imports BaseOperator at module level) ↓ airflow.models.BaseOperator (or airflow.sdk.BaseOperator) ↓ airflow.models.mappedoperator (BaseOperator imports this) ↓ airflow.triggers.base (MappedOperator imports this) ↓ airflow.models.taskinstance (triggers.base imports SimpleTaskInstance) ↓ airflow.models.xcom (TaskInstance imports XCom) ↓ resolve_xcom_backend() (tries to load XCom backend again) ↓ CIRCULAR IMPORT! 🔄 ``` Fixes apache#55803
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 7, 2025
…5805) Remove ``BaseOperator`` import from ``version_compat.py`` to prevent circular import during ``XCom`` backend resolution. The import was causing startup failures for scheduler and triggerer when XComObjectStorageBackend was configured as the XCom backend. Move ``BaseOperator`` import directly to `file_transfer.py` where it's needed, maintaining compatibility with both Airflow 2.x and 3.x while avoiding the circular dependency chain that was introduced in PR apache#52443. For use with Airflow 2.x, this is what was causing Circular import: ``` XCom Backend Resolution ↓ airflow.providers.common.io.xcom.backend ↓ airflow.providers.common.io.version_compat (imports BaseOperator at module level) ↓ airflow.models.BaseOperator (or airflow.sdk.BaseOperator) ↓ airflow.models.mappedoperator (BaseOperator imports this) ↓ airflow.triggers.base (MappedOperator imports this) ↓ airflow.models.taskinstance (triggers.base imports SimpleTaskInstance) ↓ airflow.models.xcom (TaskInstance imports XCom) ↓ resolve_xcom_backend() (tries to load XCom backend again) ↓ CIRCULAR IMPORT! 🔄 ``` Fixes apache#55803
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 8, 2025
…5805) Remove ``BaseOperator`` import from ``version_compat.py`` to prevent circular import during ``XCom`` backend resolution. The import was causing startup failures for scheduler and triggerer when XComObjectStorageBackend was configured as the XCom backend. Move ``BaseOperator`` import directly to `file_transfer.py` where it's needed, maintaining compatibility with both Airflow 2.x and 3.x while avoiding the circular dependency chain that was introduced in PR apache#52443. For use with Airflow 2.x, this is what was causing Circular import: ``` XCom Backend Resolution ↓ airflow.providers.common.io.xcom.backend ↓ airflow.providers.common.io.version_compat (imports BaseOperator at module level) ↓ airflow.models.BaseOperator (or airflow.sdk.BaseOperator) ↓ airflow.models.mappedoperator (BaseOperator imports this) ↓ airflow.triggers.base (MappedOperator imports this) ↓ airflow.models.taskinstance (triggers.base imports SimpleTaskInstance) ↓ airflow.models.xcom (TaskInstance imports XCom) ↓ resolve_xcom_backend() (tries to load XCom backend again) ↓ CIRCULAR IMPORT! 🔄 ``` Fixes apache#55803
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 9, 2025
…5805) Remove ``BaseOperator`` import from ``version_compat.py`` to prevent circular import during ``XCom`` backend resolution. The import was causing startup failures for scheduler and triggerer when XComObjectStorageBackend was configured as the XCom backend. Move ``BaseOperator`` import directly to `file_transfer.py` where it's needed, maintaining compatibility with both Airflow 2.x and 3.x while avoiding the circular dependency chain that was introduced in PR apache#52443. For use with Airflow 2.x, this is what was causing Circular import: ``` XCom Backend Resolution ↓ airflow.providers.common.io.xcom.backend ↓ airflow.providers.common.io.version_compat (imports BaseOperator at module level) ↓ airflow.models.BaseOperator (or airflow.sdk.BaseOperator) ↓ airflow.models.mappedoperator (BaseOperator imports this) ↓ airflow.triggers.base (MappedOperator imports this) ↓ airflow.models.taskinstance (triggers.base imports SimpleTaskInstance) ↓ airflow.models.xcom (TaskInstance imports XCom) ↓ resolve_xcom_backend() (tries to load XCom backend again) ↓ CIRCULAR IMPORT! 🔄 ``` Fixes apache#55803
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 10, 2025
…5805) Remove ``BaseOperator`` import from ``version_compat.py`` to prevent circular import during ``XCom`` backend resolution. The import was causing startup failures for scheduler and triggerer when XComObjectStorageBackend was configured as the XCom backend. Move ``BaseOperator`` import directly to `file_transfer.py` where it's needed, maintaining compatibility with both Airflow 2.x and 3.x while avoiding the circular dependency chain that was introduced in PR apache#52443. For use with Airflow 2.x, this is what was causing Circular import: ``` XCom Backend Resolution ↓ airflow.providers.common.io.xcom.backend ↓ airflow.providers.common.io.version_compat (imports BaseOperator at module level) ↓ airflow.models.BaseOperator (or airflow.sdk.BaseOperator) ↓ airflow.models.mappedoperator (BaseOperator imports this) ↓ airflow.triggers.base (MappedOperator imports this) ↓ airflow.models.taskinstance (triggers.base imports SimpleTaskInstance) ↓ airflow.models.xcom (TaskInstance imports XCom) ↓ resolve_xcom_backend() (tries to load XCom backend again) ↓ CIRCULAR IMPORT! 🔄 ``` Fixes apache#55803
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 11, 2025
…5805) Remove ``BaseOperator`` import from ``version_compat.py`` to prevent circular import during ``XCom`` backend resolution. The import was causing startup failures for scheduler and triggerer when XComObjectStorageBackend was configured as the XCom backend. Move ``BaseOperator`` import directly to `file_transfer.py` where it's needed, maintaining compatibility with both Airflow 2.x and 3.x while avoiding the circular dependency chain that was introduced in PR apache#52443. For use with Airflow 2.x, this is what was causing Circular import: ``` XCom Backend Resolution ↓ airflow.providers.common.io.xcom.backend ↓ airflow.providers.common.io.version_compat (imports BaseOperator at module level) ↓ airflow.models.BaseOperator (or airflow.sdk.BaseOperator) ↓ airflow.models.mappedoperator (BaseOperator imports this) ↓ airflow.triggers.base (MappedOperator imports this) ↓ airflow.models.taskinstance (triggers.base imports SimpleTaskInstance) ↓ airflow.models.xcom (TaskInstance imports XCom) ↓ resolve_xcom_backend() (tries to load XCom backend again) ↓ CIRCULAR IMPORT! 🔄 ``` Fixes apache#55803
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 12, 2025
…5805) Remove ``BaseOperator`` import from ``version_compat.py`` to prevent circular import during ``XCom`` backend resolution. The import was causing startup failures for scheduler and triggerer when XComObjectStorageBackend was configured as the XCom backend. Move ``BaseOperator`` import directly to `file_transfer.py` where it's needed, maintaining compatibility with both Airflow 2.x and 3.x while avoiding the circular dependency chain that was introduced in PR apache#52443. For use with Airflow 2.x, this is what was causing Circular import: ``` XCom Backend Resolution ↓ airflow.providers.common.io.xcom.backend ↓ airflow.providers.common.io.version_compat (imports BaseOperator at module level) ↓ airflow.models.BaseOperator (or airflow.sdk.BaseOperator) ↓ airflow.models.mappedoperator (BaseOperator imports this) ↓ airflow.triggers.base (MappedOperator imports this) ↓ airflow.models.taskinstance (triggers.base imports SimpleTaskInstance) ↓ airflow.models.xcom (TaskInstance imports XCom) ↓ resolve_xcom_backend() (tries to load XCom backend again) ↓ CIRCULAR IMPORT! 🔄 ``` Fixes apache#55803
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 14, 2025
…5805) Remove ``BaseOperator`` import from ``version_compat.py`` to prevent circular import during ``XCom`` backend resolution. The import was causing startup failures for scheduler and triggerer when XComObjectStorageBackend was configured as the XCom backend. Move ``BaseOperator`` import directly to `file_transfer.py` where it's needed, maintaining compatibility with both Airflow 2.x and 3.x while avoiding the circular dependency chain that was introduced in PR apache#52443. For use with Airflow 2.x, this is what was causing Circular import: ``` XCom Backend Resolution ↓ airflow.providers.common.io.xcom.backend ↓ airflow.providers.common.io.version_compat (imports BaseOperator at module level) ↓ airflow.models.BaseOperator (or airflow.sdk.BaseOperator) ↓ airflow.models.mappedoperator (BaseOperator imports this) ↓ airflow.triggers.base (MappedOperator imports this) ↓ airflow.models.taskinstance (triggers.base imports SimpleTaskInstance) ↓ airflow.models.xcom (TaskInstance imports XCom) ↓ resolve_xcom_backend() (tries to load XCom backend again) ↓ CIRCULAR IMPORT! 🔄 ``` Fixes apache#55803
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 15, 2025
…5805) Remove ``BaseOperator`` import from ``version_compat.py`` to prevent circular import during ``XCom`` backend resolution. The import was causing startup failures for scheduler and triggerer when XComObjectStorageBackend was configured as the XCom backend. Move ``BaseOperator`` import directly to `file_transfer.py` where it's needed, maintaining compatibility with both Airflow 2.x and 3.x while avoiding the circular dependency chain that was introduced in PR apache#52443. For use with Airflow 2.x, this is what was causing Circular import: ``` XCom Backend Resolution ↓ airflow.providers.common.io.xcom.backend ↓ airflow.providers.common.io.version_compat (imports BaseOperator at module level) ↓ airflow.models.BaseOperator (or airflow.sdk.BaseOperator) ↓ airflow.models.mappedoperator (BaseOperator imports this) ↓ airflow.triggers.base (MappedOperator imports this) ↓ airflow.models.taskinstance (triggers.base imports SimpleTaskInstance) ↓ airflow.models.xcom (TaskInstance imports XCom) ↓ resolve_xcom_backend() (tries to load XCom backend again) ↓ CIRCULAR IMPORT! 🔄 ``` Fixes apache#55803
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 17, 2025
…5805) Remove ``BaseOperator`` import from ``version_compat.py`` to prevent circular import during ``XCom`` backend resolution. The import was causing startup failures for scheduler and triggerer when XComObjectStorageBackend was configured as the XCom backend. Move ``BaseOperator`` import directly to `file_transfer.py` where it's needed, maintaining compatibility with both Airflow 2.x and 3.x while avoiding the circular dependency chain that was introduced in PR apache#52443. For use with Airflow 2.x, this is what was causing Circular import: ``` XCom Backend Resolution ↓ airflow.providers.common.io.xcom.backend ↓ airflow.providers.common.io.version_compat (imports BaseOperator at module level) ↓ airflow.models.BaseOperator (or airflow.sdk.BaseOperator) ↓ airflow.models.mappedoperator (BaseOperator imports this) ↓ airflow.triggers.base (MappedOperator imports this) ↓ airflow.models.taskinstance (triggers.base imports SimpleTaskInstance) ↓ airflow.models.xcom (TaskInstance imports XCom) ↓ resolve_xcom_backend() (tries to load XCom backend again) ↓ CIRCULAR IMPORT! 🔄 ``` Fixes apache#55803
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 19, 2025
…5805) Remove ``BaseOperator`` import from ``version_compat.py`` to prevent circular import during ``XCom`` backend resolution. The import was causing startup failures for scheduler and triggerer when XComObjectStorageBackend was configured as the XCom backend. Move ``BaseOperator`` import directly to `file_transfer.py` where it's needed, maintaining compatibility with both Airflow 2.x and 3.x while avoiding the circular dependency chain that was introduced in PR apache#52443. For use with Airflow 2.x, this is what was causing Circular import: ``` XCom Backend Resolution ↓ airflow.providers.common.io.xcom.backend ↓ airflow.providers.common.io.version_compat (imports BaseOperator at module level) ↓ airflow.models.BaseOperator (or airflow.sdk.BaseOperator) ↓ airflow.models.mappedoperator (BaseOperator imports this) ↓ airflow.triggers.base (MappedOperator imports this) ↓ airflow.models.taskinstance (triggers.base imports SimpleTaskInstance) ↓ airflow.models.xcom (TaskInstance imports XCom) ↓ resolve_xcom_backend() (tries to load XCom backend again) ↓ CIRCULAR IMPORT! 🔄 ``` Fixes apache#55803
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.
Remove
BaseOperatorimport fromversion_compat.pyto prevent circular import duringXCombackend resolution. The import was causing startup failures for scheduler and triggerer when XComObjectStorageBackend was configured as the XCom backend.Move
BaseOperatorimport directly tofile_transfer.pywhere it's needed, maintaining compatibility with both Airflow 2.x and 3.x while avoiding the circular dependency chain that was introduced in PR #52443.For use with Airflow 2.x, this is what was causing Circular import:
Fixes #55803
To Reproduce:
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.