Skip to content

Conversation

@gopidesupavan
Copy link
Member


^ 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.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

@gopidesupavan gopidesupavan added the backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch label May 6, 2025
@potiuk
Copy link
Member

potiuk commented May 6, 2025

Nice! Thanks !

@gopidesupavan
Copy link
Member Author

backporting this change just to CI works in v3 without issues

@potiuk potiuk merged commit 8c0dcc8 into apache:main May 6, 2025
18 checks passed
@gopidesupavan
Copy link
Member Author

cc: @kaxil

@github-actions
Copy link

github-actions bot commented May 6, 2025

Backport failed to create: v3-0-test. View the failure log Run details

Status Branch Result
v3-0-test Commit Link

You can attempt to backport this manually by running:

cherry_picker 8c0dcc8 v3-0-test

This should apply the commit to the v3-0-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

gopidesupavan added a commit to gopidesupavan/airflow that referenced this pull request May 6, 2025
potiuk pushed a commit that referenced this pull request May 7, 2025
ayush3singh pushed a commit to ayush3singh/airflow that referenced this pull request May 8, 2025
kaxil pushed a commit that referenced this pull request Jun 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:dev-tools backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants