CI: Build CI image after Dockerfiles are updated in breeze ci upgrade#64777
Merged
Conversation
potiuk
requested review from
amoghrajesh,
ashb,
bugraoz93,
choo121600,
ephraimbuddy,
gopidesupavan,
jason810496,
jedcunningham,
jscheffl and
vatsrahul1001
as code owners
potiuk
removed request for
ashb,
bugraoz93,
choo121600,
ephraimbuddy,
gopidesupavan,
jason810496,
jedcunningham,
jscheffl and
vatsrahul1001
potiuk
requested review from
Dev-iL,
Lee-W,
bugraoz93,
choo121600,
eladkal,
ephraimbuddy,
gopidesupavan and
jason810496
jscheffl
approved these changes
Apr 6, 2026
github-actions Bot
pushed a commit
that referenced
this pull request
Apr 6, 2026
…e ci upgrade (#64777) (cherry picked from commit b875c40) Co-authored-by: Jarek Potiuk <[email protected]>
Contributor
Backport successfully created: v3-2-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
potiuk
added a commit
that referenced
this pull request
Apr 6, 2026
…e ci upgrade (#64777) (cherry picked from commit b875c40) Co-authored-by: Jarek Potiuk <[email protected]>
potiuk
added a commit
that referenced
this pull request
Apr 6, 2026
…e ci upgrade (#64777) (#64781) (cherry picked from commit b875c40) Co-authored-by: Jarek Potiuk <[email protected]>
Dev-iL
reviewed
Apr 6, 2026
| else: | ||
| console_print(f"[info]Skipping {step_name} (disabled).[/]") | ||
|
|
||
| # Build the CI image for Python 3.10 after Dockerfiles have been updated so that |
Collaborator
There was a problem hiding this comment.
Why is 3.10 mentioned specifically? Was this not an issue in other versions?
Contributor
There was a problem hiding this comment.
We decided to always use lowest version in CI to ensure that we are really compatible to the oldest supported Python version.
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 8, 2026
…e ci upgrade (#64777) (#64781) (cherry picked from commit b875c40) Co-authored-by: Jarek Potiuk <[email protected]>
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 15, 2026
…e ci upgrade (#64777) (#64781) (cherry picked from commit b875c40) Co-authored-by: Jarek Potiuk <[email protected]>
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 15, 2026
…e ci upgrade (#64777) (#64781) (cherry picked from commit b875c40) Co-authored-by: Jarek Potiuk <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Previously,
breeze ci upgradebuilt the CI image before runningupgrade-important-versions, which updates Dockerfiles. This meantthe
update-uv-lockstep (which runs inside the image) used a staleimage that didn't reflect the Dockerfile changes.
Now the upgrade commands are split into two phases:
breeze ci-image build --python 3.10Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Claude Opus 4.6) following the guidelines