potiuk opened a new pull request, #73318:
URL: https://github.com/apache/airflow/pull/73318

   `3.3.x` is the release branch under active maintenance — it took commits 
today — but nothing has been refreshing its pinned uv, prek and image versions, 
because the only scheduled caller targets `main`. Those pins drift on a release 
branch the same way they do on `main`; until now they were refreshed by running 
`breeze ci upgrade --target-branch v3-3-test` by hand (most recently #73042).
   
   `v3-2-test` carried an identical caller until #68275 removed it, on the 
grounds that no further 3.2.x releases were planned. This restores the same 
arrangement for the branch that *is* taking releases.
   
   The reusable `upgrade-check.yml` is already fully parameterised on 
`target-branch`: it checks out that ref, and looks the PR up with `--head 
ci-upgrade-${TARGET_BRANCH} --base ${TARGET_BRANCH}`. `breeze ci upgrade` 
validates its target against `^(main|v\d+-\d+-test)$`, so `v3-3-test` is a 
supported value by design — no change was needed on either side.
   
   Schedule is Tue/Thu 06:00 UTC, the days `main` does not run, mirroring what 
`v3-2-test` used so the two never overlap.
   
   When 3.3.x stops taking releases this file should be deleted, the way #68275 
did for 3.2.
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — Claude Code (Opus 5)
   
   Generated-by: Claude Code (Opus 5) following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   


-- 
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]

Reply via email to