kevinveenbirkenbachandClaude Opus 5 73b594b004 fix(mirror): keep a variant tag out of the version a role deploys ...

d6d7ff8c9e made iter_role_images yield one ref per version_variants suffix so
the mirror copies the extra tags. Two of its four consumers assumed one ref per
service. The resolver writes services[service] = {image, version}, so the last
ref won and the applications override carried v1.9.6-cuda; the engine role
appends -cuda itself and asked the mirror for v1.9.6-cuda-cuda, a tag nothing
ever pushed. The version updater builds one entry per ref and writes back into
meta/services.yml, so it would have replaced the declared version with a cuda
tag once this branch reaches the bot on main.

ImageRef now carries `derived`. The resolver and the updater skip those refs;
the mirror sync keeps iterating all of them, which is what the variants exist
for, and the mirror wait already keyed on the full ref including the version.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-10-04 21:15:04 +02:00

..

__init__.py

…

test_healthcheck.py

Merge remote-tracking branch 'upstream/main' into feature/role-stalwart-mail-swarm

2026-09-21 03:25:20 +04:00

test_image_discovery_variants.py

fix(mirror): keep a variant tag out of the version a role deploys

2026-10-04 21:15:04 +02:00

test_image_pin.py

style(quality): apply what the gate wrote back into the tree

2026-09-17 19:35:05 +02:00

test_image_ref.py

…

test_mirror.py

…

test_registry_healthcheck.py

…

test_registry.py

…