Skip to content

Conversation

@potiuk
Copy link
Member

@potiuk potiuk commented Oct 31, 2025

There was an RC tagging problem with tagging providers when releasing this PR brings back tag-providers and separates tagging providers with date to a separate message


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

There was an RC tagging problem with tagging providers when releasing
this PR brings back tag-providers and separates tagging providers with
date to a separate message
@eladkal eladkal merged commit 8736710 into apache:main Nov 1, 2025
117 checks passed
@github-actions
Copy link

github-actions bot commented Nov 1, 2025

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

Status Branch Result
v3-1-test Commit Link

You can attempt to backport this manually by running:

cherry_picker 8736710 v3-1-test

This should apply the commit to the v3-1-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

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.

4 participants