Skip to content

Update release process for providers to use RAT 0.17#57201

Merged
potiuk merged 1 commit intoapache:mainfrom
potiuk:update-release-verification-for-providers
Oct 24, 2025
Merged

Update release process for providers to use RAT 0.17#57201
potiuk merged 1 commit intoapache:mainfrom
potiuk:update-release-verification-for-providers

Conversation

@potiuk
Copy link
Copy Markdown
Member

@potiuk potiuk commented Oct 24, 2025

RAT 0.17 has been released recently and it was quite a big change. While we cannot use archive check that was released in 0.17 due to bug https://issues.apache.org/jira/projects/RAT/issues/RAT-511 we should still switch to it as it is going to be used in the Apache Trusted Releases soon.

This change adds missing .rat-excludes and also updates the process to produce nicer output.


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

RAT 0.17 has been released recently and it was quite a big change.
While we cannot use archive check that was released in 0.17
due to bug https://issues.apache.org/jira/projects/RAT/issues/RAT-511
we should still switch to it as it is going to be used in the
Apache Trusted Releases soon.

This change adds missing .rat-excludes and also updates the process
to produce nicer output.
Copy link
Copy Markdown
Contributor

@amoghrajesh amoghrajesh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah nice

@potiuk potiuk merged commit 78837ef into apache:main Oct 24, 2025
61 checks passed
@potiuk potiuk deleted the update-release-verification-for-providers branch October 24, 2025 16:03
@github-actions
Copy link
Copy Markdown

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 78837ef 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.

2 participants