potiuk opened a new pull request, #65243:
URL: https://github.com/apache/airflow/pull/65243
…ck + Slack alerts (#65211)
Removes all hard-coded uv/prek version strings from GitHub Actions workflows
and composite actions and derives them at runtime from 'uv.lock' via a small
sed snippet. Also adds Slack success and failure notifications to the scheduled
CI upgrade workflow.
Why: the scheduled '[v3-2-test] Scheduled CI upgrade check' job was failing
because 'breeze ci upgrade' kept rewriting version strings in
'.github/workflows/*.yml' files, which the default GITHUB_TOKEN (a GitHub App
token) is not permitted to push. Reading versions from 'uv.lock' (which gets
refreshed by 'uv lock --upgrade' as part of the upgrade run anyway) means the
job no longer needs to touch any file under '.github/workflows/' and its PR can
be created using only the standard GITHUB_TOKEN — no PAT or GitHub App required.
Notifications to '#internal-airflow-ci-cd' now fire on both success (with PR
link and Undraft -> Review -> Merge-once-CI-passes steps) and failure (with a
link to the failed run). The branch prefix (e.g. '[main]' vs '[v3-2-test]')
distinguishes notifications between the schedules.
(cherry picked from commit c66d54075b93b9e538d12bc4f536ec96c0e5fafb)
<!-- 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:
http://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.
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]
