Skip to content

Conversation

@gopidesupavan
Copy link
Member

This is followup of #54272 Noticed we always consider backreferences from main. Now we are validation versions by publishing package we should refer the current PR workflow branch to use redirects.


^ 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.

@boring-cyborg boring-cyborg bot added area:dev-tools backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch labels Aug 9, 2025
@gopidesupavan gopidesupavan requested a review from eladkal August 9, 2025 13:01
@gopidesupavan
Copy link
Member Author

failure test not related..

@gopidesupavan gopidesupavan merged commit 0c347b4 into apache:main Aug 9, 2025
100 of 101 checks passed
@github-actions
Copy link

github-actions bot commented Aug 9, 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 0c347b4 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

@potiuk
Copy link
Member

potiuk commented Aug 10, 2025

NICE!

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.

3 participants