Repository navigation
Replace upgrade-check build failure with scheduled upgrade PR workflow - #64836
Conversation
Move upgrade checks from basic-tests.yml (where they failed the build) to a scheduled workflow that runs Mon/Wed/Fri for main and Tue/Thu for v3-2-test. The workflow uses `breeze ci upgrade` to run all upgrade steps and create a draft PR. A Slack notification is sent to #internal-airflow-ci-cd when a PR needs review. Changes: - Remove upgrade-check job from basic-tests.yml - Add reusable upgrade-check.yml workflow (workflow_call) - Add scheduled-upgrade-check.yml caller (cron + workflow_dispatch) - Enhance breeze ci upgrade: --draft flag, stable branch naming, existing PR detection, no -w flag for CI compatibility
Backport failed to create: v3-2-test. View the failure log Run detailsNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
You can attempt to backport this manually by running: cherry_picker dd0ff5a v3-2-testThis should apply the commit to the v3-2-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 --continueIf you don't have cherry-picker installed, see the installation guide. |
jscheffl
left a comment
There was a problem hiding this comment.
Cool!
Mini follow-up we need to check, if change from tooling requires code adjustments (like Mypy upgrade last week) then the commit is failing in pre-commit checks. So probably we need to change that commits are automated skipping pre-merge checks... but can be a follow-up as well.
apache#64836) Move upgrade checks from basic-tests.yml (where they failed the build) to a scheduled workflow that runs Mon/Wed/Fri for main and Tue/Thu for v3-2-test. The workflow uses `breeze ci upgrade` to run all upgrade steps and create a draft PR. A Slack notification is sent to #internal-airflow-ci-cd when a PR needs review. Changes: - Remove upgrade-check job from basic-tests.yml - Add reusable upgrade-check.yml workflow (workflow_call) - Add scheduled-upgrade-check.yml caller (cron + workflow_dispatch) - Enhance breeze ci upgrade: --draft flag, stable branch naming, existing PR detection, no -w flag for CI compatibility
…e PR workflow (#64836) Move upgrade checks from basic-tests.yml (where they failed the build) to a scheduled workflow that runs Mon/Wed/Fri for main and Tue/Thu for v3-2-test. The workflow uses `breeze ci upgrade` to run all upgrade steps and create a draft PR. A Slack notification is sent to #internal-airflow-ci-cd when a PR needs review. Changes: - Remove upgrade-check job from basic-tests.yml - Add reusable upgrade-check.yml workflow (workflow_call) - Add scheduled-upgrade-check.yml caller (cron + workflow_dispatch) - Enhance breeze ci upgrade: --draft flag, stable branch naming, existing PR detection, no -w flag for CI compatibility (cherry picked from commit dd0ff5a) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
…e PR workflow (#64836) (#64915) Move upgrade checks from basic-tests.yml (where they failed the build) to a scheduled workflow that runs Mon/Wed/Fri for main and Tue/Thu for v3-2-test. The workflow uses `breeze ci upgrade` to run all upgrade steps and create a draft PR. A Slack notification is sent to #internal-airflow-ci-cd when a PR needs review. Changes: - Remove upgrade-check job from basic-tests.yml - Add reusable upgrade-check.yml workflow (workflow_call) - Add scheduled-upgrade-check.yml caller (cron + workflow_dispatch) - Enhance breeze ci upgrade: --draft flag, stable branch naming, existing PR detection, no -w flag for CI compatibility (cherry picked from commit dd0ff5a)
…e PR workflow (#64836) (#64915) Move upgrade checks from basic-tests.yml (where they failed the build) to a scheduled workflow that runs Mon/Wed/Fri for main and Tue/Thu for v3-2-test. The workflow uses `breeze ci upgrade` to run all upgrade steps and create a draft PR. A Slack notification is sent to #internal-airflow-ci-cd when a PR needs review. Changes: - Remove upgrade-check job from basic-tests.yml - Add reusable upgrade-check.yml workflow (workflow_call) - Add scheduled-upgrade-check.yml caller (cron + workflow_dispatch) - Enhance breeze ci upgrade: --draft flag, stable branch naming, existing PR detection, no -w flag for CI compatibility (cherry picked from commit dd0ff5a)
…e PR workflow (#64836) (#64915) Move upgrade checks from basic-tests.yml (where they failed the build) to a scheduled workflow that runs Mon/Wed/Fri for main and Tue/Thu for v3-2-test. The workflow uses `breeze ci upgrade` to run all upgrade steps and create a draft PR. A Slack notification is sent to #internal-airflow-ci-cd when a PR needs review. Changes: - Remove upgrade-check job from basic-tests.yml - Add reusable upgrade-check.yml workflow (workflow_call) - Add scheduled-upgrade-check.yml caller (cron + workflow_dispatch) - Enhance breeze ci upgrade: --draft flag, stable branch naming, existing PR detection, no -w flag for CI compatibility (cherry picked from commit dd0ff5a)
…e PR workflow (#64836) (#64915) Move upgrade checks from basic-tests.yml (where they failed the build) to a scheduled workflow that runs Mon/Wed/Fri for main and Tue/Thu for v3-2-test. The workflow uses `breeze ci upgrade` to run all upgrade steps and create a draft PR. A Slack notification is sent to #internal-airflow-ci-cd when a PR needs review. Changes: - Remove upgrade-check job from basic-tests.yml - Add reusable upgrade-check.yml workflow (workflow_call) - Add scheduled-upgrade-check.yml caller (cron + workflow_dispatch) - Enhance breeze ci upgrade: --draft flag, stable branch naming, existing PR detection, no -w flag for CI compatibility (cherry picked from commit dd0ff5a)
…e PR workflow (#64836) (#64915) Move upgrade checks from basic-tests.yml (where they failed the build) to a scheduled workflow that runs Mon/Wed/Fri for main and Tue/Thu for v3-2-test. The workflow uses `breeze ci upgrade` to run all upgrade steps and create a draft PR. A Slack notification is sent to #internal-airflow-ci-cd when a PR needs review. Changes: - Remove upgrade-check job from basic-tests.yml - Add reusable upgrade-check.yml workflow (workflow_call) - Add scheduled-upgrade-check.yml caller (cron + workflow_dispatch) - Enhance breeze ci upgrade: --draft flag, stable branch naming, existing PR detection, no -w flag for CI compatibility (cherry picked from commit dd0ff5a)
Since #76251 the CI docs sent readers to the wrong workflow and claimed that canaries with failed jobs save no report inputs. Those canaries now get a report, with its explanation jobs, so anyone estimating report runs or their cost from the docs would come out too low. The docs also still credited basic tests with upgrade monitoring, which left since #64836, so a reader looking for this check got two answers. Generated-by: Claude Opus 5
…76439) (#76454) Since #76251 the CI docs sent readers to the wrong workflow and claimed that canaries with failed jobs save no report inputs. Those canaries now get a report, with its explanation jobs, so anyone estimating report runs or their cost from the docs would come out too low. The docs also still credited basic tests with upgrade monitoring, which left since #64836, so a reader looking for this check got two answers. (cherry picked from commit 629729a) Generated-by: Claude Opus 5 Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
…76439) (#76454) Since #76251 the CI docs sent readers to the wrong workflow and claimed that canaries with failed jobs save no report inputs. Those canaries now get a report, with its explanation jobs, so anyone estimating report runs or their cost from the docs would come out too low. The docs also still credited basic tests with upgrade monitoring, which left since #64836, so a reader looking for this check got two answers. (cherry picked from commit 629729a) Generated-by: Claude Opus 5 Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
…76439) (#76454) Since #76251 the CI docs sent readers to the wrong workflow and claimed that canaries with failed jobs save no report inputs. Those canaries now get a report, with its explanation jobs, so anyone estimating report runs or their cost from the docs would come out too low. The docs also still credited basic tests with upgrade monitoring, which left since #64836, so a reader looking for this check got two answers. (cherry picked from commit 629729a) Generated-by: Claude Opus 5 Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
…76439) (#76454) Since #76251 the CI docs sent readers to the wrong workflow and claimed that canaries with failed jobs save no report inputs. Those canaries now get a report, with its explanation jobs, so anyone estimating report runs or their cost from the docs would come out too low. The docs also still credited basic tests with upgrade monitoring, which left since #64836, so a reader looking for this check got two answers. (cherry picked from commit 629729a) Generated-by: Claude Opus 5 Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
…76439) (#76454) Since #76251 the CI docs sent readers to the wrong workflow and claimed that canaries with failed jobs save no report inputs. Those canaries now get a report, with its explanation jobs, so anyone estimating report runs or their cost from the docs would come out too low. The docs also still credited basic tests with upgrade monitoring, which left since #64836, so a reader looking for this check got two answers. (cherry picked from commit 629729a) Generated-by: Claude Opus 5 Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
…76439) (#76454) Since #76251 the CI docs sent readers to the wrong workflow and claimed that canaries with failed jobs save no report inputs. Those canaries now get a report, with its explanation jobs, so anyone estimating report runs or their cost from the docs would come out too low. The docs also still credited basic tests with upgrade monitoring, which left since #64836, so a reader looking for this check got two answers. (cherry picked from commit 629729a) Generated-by: Claude Opus 5 Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
Move upgrade checks from basic-tests.yml (where they failed the build) to
scheduled workflows that create draft PRs with the changes:
The workflows use
breeze ci upgradein non-interactive mode. When upgradesare found, a draft PR is created (or an existing one is updated via force push
and converted back to draft). A Slack notification is sent to
#internal-airflow-ci-cdso a human can undraft, review and merge.Changes:
upgrade-checkjob frombasic-tests.ymlupgrade-check.ymlworkflow (workflow_call)scheduled-upgrade-check-main.yml(Mon/Wed/Fri cron)scheduled-upgrade-check-v3-2-test.yml(Tue/Thu cron)breeze ci upgrade:--draftflag, stable branch naming(
ci-upgrade-{branch}), existing PR detection, removed-wflagfor CI compatibility
ci_commands_config.pywith new--draftoptionWas generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Claude Opus 4.6) following the guidelines