-
Notifications
You must be signed in to change notification settings - Fork 16.3k
Review and modernize release check process for Airflow: #57203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Review and modernize release check process for Airflow: #57203
Conversation
b2bcd35 to
a00c51b
Compare
* include task-sdk * switch to RAT 0.17 * update .rat-excludes to be compatible with RAT 0.17 * Add .gitignore to task-sdk to not build release with accidental files
a00c51b to
6eefea2
Compare
jscheffl
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
Backport failed to create: v3-1-test. View the failure log Run details
You can attempt to backport this manually by running: cherry_picker 90e3926 v3-1-testThis should apply the commit to the v3-1-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continue |
…pache#57203) * include task-sdk * switch to RAT 0.17 * update .rat-excludes to be compatible with RAT 0.17 * Add .gitignore to task-sdk to not build release with accidental files (cherry picked from commit 90e3926) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
…pache#57203) * include task-sdk * switch to RAT 0.17 * update .rat-excludes to be compatible with RAT 0.17 * Add .gitignore to task-sdk to not build release with accidental files (cherry picked from commit 90e3926) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
^ 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.