[v3-2-test] Fix registry backfill with per-provider versions and Docker extraction (#65223)#66927
Open
vatsrahul1001 wants to merge 1 commit into
Open
[v3-2-test] Fix registry backfill with per-provider versions and Docker extraction (#65223)#66927vatsrahul1001 wants to merge 1 commit into
vatsrahul1001 wants to merge 1 commit into
Conversation
vatsrahul1001
requested review from
amoghrajesh,
ashb,
bugraoz93,
choo121600,
ephraimbuddy,
gopidesupavan,
jason810496,
jedcunningham,
jscheffl,
kaxil and
potiuk
as code owners
vatsrahul1001
force-pushed
the
backport-322-65223
branch
from
8a706b1 to
47948c5
Compare
1 task
vatsrahul1001
added
the
changelog:skip
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
2 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.
Cherry-pick of #65223 for the Airflow 3.2.2 patch release.
Backported as a prerequisite for #66311 (Breeze `down` discovery), which depends on the `_backfill_docker` function and `--use-docker/--no-docker` flag introduced here.
Conflict resolution
One conflict in `.github/workflows/registry-backfill.yml`. v3-2-test used a two-step "Install uv" + "Install Breeze" flow (with `astral-sh/setup-uv@v8.1.0` pinned); upstream consolidated into the composite `./.github/actions/prepare_breeze_and_image` action. That composite action does exist on v3-2-test, so adopted the PR's consolidated step with no functional regression. The composite action handles uv installation internally with its own pinned version.
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.7) following the guidelines