Repository navigation
fix(release): push chromium's index without annotations, which buildx refuses on a Docker manifest list - #798
Merged
earakely-scale merged 1 commit intoNov 19, 2026
Conversation
… refuses on a Docker manifest list A compose pushes each arch's image with docker push, so the images have Docker media types, and the buildx on GitHub's newer runner image (20261116.202.1) refuses index annotations over a Docker manifest list. v0.9.1573's computer-publish failed that way and the release recorded no chromium. agentenv-chromium is already public and linked to the repo, and the annotations were metadata only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
earakely-scale
deleted the
edgararakelyan/fd-6305-chromiums-release-publish-fails-on
branch
November 19, 2026 01:56
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
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.
What
The release's
computer-publishpushes each composed computer app's index (today, chromium's) without the two index annotations (org.opencontainers.image.source,org.opencontainers.image.revision).Why
v0.9.1573 published no chromium:
A compose pushes each arch's image with
docker push, which gives the images Docker media types. The buildx on GitHub's newer runner image (20261116.202.1) refuses index annotations over a Docker manifest list. The older image (20261111.196.1) let them through, which is why v0.9.1572 and v0.9.1574 published and v0.9.1573 didn't:Once GitHub has moved every runner to the newer image, every release would fail to publish chromium. Its record would then lack chromium, and the sdk would refuse chromium's promotion.
agentenv-chromiumis already public and linked to this repo, and the annotations were metadata only. The infra images' own publish keeps its annotations: those images are built with buildx, as OCI.Not chosen (Edgar, Nov 18): adding the source label to each composed image as well, or having the composer push OCI media types, which would change every compose.
Tests
test_publish_computers_joins_each_apps_platform_manifests_into_one_index_and_records_itexpects the command without the annotations.tst/unit/test_infra_build_script.py: 80 passed.FD-6305
🤖 Generated with Claude Code


Confidence Score: 5/5
This PR appears safe to merge.Summary
Removes source and revision annotations from composed computer indexes so Chromium publishing avoids buildx's Docker manifest-list restriction.
The PR description records that Edgar deferred adding source labels or changing the composer to push OCI media types because those alternatives would affect every compose.
Reviews (1) · Last reviewed commit: "fix(release): push chromium's index with..." · Reviewed by Greptile