Adding change in xcom_pull behaviour to release notes
#49455
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
Contributor
Author
2 tasks
amoghrajesh
force-pushed
the
xcom-pull-doc
branch
from
b9d5bf5 to
6230511
Compare
amoghrajesh
changed the title
xcom_pull behaviour to release notes
kaxil
reviewed
Apr 22, 2025
kaxil
reviewed
Apr 22, 2025
kaxil
reviewed
Apr 22, 2025
Co-authored-by: Kaxil Naik <kaxilnaik@gmail.com>
Contributor
|
@amoghrajesh @kaxil what do you think about adding information about |
kaxil
pushed a commit
that referenced
this pull request
Apr 22, 2025
(cherry picked from commit dda8626)
prabhusneha
pushed a commit
to astronomer/airflow
that referenced
this pull request
Apr 25, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Theres a change in behaviour in xcom_pull, for the better and to make it less ambiguous.
Adding to migration docs so folks dont miss it and dont rely on old behaviour.
^ 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.