potiuk opened a new pull request, #73068: URL: https://github.com/apache/airflow/pull/73068
…RAT 0.18 (#73064) * Make the RAT licence check ignore IntelliJ module files again The exclude entry for these was written as a regex, .*\.iml, but RAT matches exclude patterns as globs against the full path. That form needs two dots to match, so airflow-core.iml and its 76 siblings never matched it and the check reported 77 unapproved licences for anyone who had opened the repo in IntelliJ. The files are gitignored and so never reach a source tarball, which is why the release-time check stayed green and the breakage only ever showed up locally. Use the same **/ form the rest of the file already uses for patterns that have to match at any depth. Generated-by: Claude Opus 5 Claude-Session: https://claude.ai/code/session_012zrnHJHPchB83FtwrYRf5q * Rebuild the Apache RAT image on RAT 0.18 The image reference has stayed on RAT 0.17 since 0.18 was adopted everywhere else, because the 0.18 image was never built: the release docs, the release validator and this script were all moved to 0.18, but no 0.18 tag was ever pushed, so the prek hook kept pulling the 0.17 image. Dating the image afresh gives the 0.18 build a tag of its own rather than overwriting a published one. Generated-by: Claude Opus 5 Claude-Session: https://claude.ai/code/session_012zrnHJHPchB83FtwrYRf5q * Run the licence check on Apache RAT 0.18 This was the one reference left behind when RAT 0.18 was adopted, so the check has been running 0.17 while the release docs and the release validator told everyone else to use 0.18. Point it at the freshly built 0.18 image, pinned by index digest as before so both architectures resolve. Generated-by: Claude Opus 5 Claude-Session: https://claude.ai/code/session_012zrnHJHPchB83FtwrYRf5q --------- (cherry picked from commit ba7a45e89828516928eb123914138363debcb3e3) <!-- SPDX-License-Identifier: Apache-2.0 https://www.apache.org/licenses/LICENSE-2.0 --> <!-- Thank you for contributing! Please provide above a brief description of the changes made in this pull request. Write a good git commit message following this guide: https://chris.beams.io/posts/git-commit/ Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. For user-facing UI changes, please attach before/after screenshots (or a short screen recording) so reviewers can assess the visual impact. Feel free to ping (in general) for the review if you do not see reaction for a few days (72 Hours is the minimum reaction time you can expect from volunteers) - we sometimes miss notifications. In case of an existing issue, reference it using one of the following: * closes: #ISSUE * related: #ISSUE --> --- ##### Was generative AI tooling used to co-author this PR? <!-- If generative AI tooling has been used in the process of authoring this PR, please change below checkbox to `[X]` followed by the name of the tool, uncomment the "Generated-by". --> - [ ] Yes (please specify the tool below) <!-- Generated-by: [Tool Name] following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) --> --- * Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)** for more information. Note: commit author/co-author name and email in commits become permanently public when merged. * For fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed. * When adding dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). * For significant user-facing changes create newsfragment: `{pr_number}.significant.rst`, in [airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments). You can add this file in a follow-up commit after the PR is created so you know the PR number. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
