Repository navigation
fix(release): try chromium's first index push again while GHCR links its new package - #717
Merged
earakely-scale merged 1 commit intoNov 16, 2026
Conversation
…its new package v0.9.1545's computer-publish created ghcr.io/scaleapi/agentenv-chromium with one arch's manifest and had the other's refused (permission_denied: write_package), since `imagetools create` pushes both at once and GHCR links a new package to the repository only after the first push. The retry already waits that out for `docker push`; it now covers `docker buildx imagetools create` too. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
earakely-scale
deleted the
edgararakelyan/fd-5908-retry-first-index-push
branch
November 16, 2026 21:04
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 and why
M8.60 (FD-5908): v0.9.1545 composed chromium on both arches but shipped without it, because its first push to GHCR was half refused.
computer-publishjoins the two arches' images into one index withdocker buildx imagetools create, which pushes both manifests at once. The first push createdghcr.io/scaleapi/agentenv-chromium. The second was refused with403 Forbidden ... denied: permission_denied: write_package, because GHCR links a new package to the repository only after its first push.infra_build.py's retry already waits that refusal out (_NOT_YET_LINKED), but only fordocker push, so nothing tried again and the job failed. The release then shipped without chromium, as designed, with a warning.What changes
infra_build.py: the retry treatsdocker buildx imagetools createas a push, so awrite_packagerefusal of either is tried again after 30, 60 and 120 s. Other commands that GHCR refuses still fail at once.What v0.9.1545 left
computersrecord, so its installs compose chromium as before.How it was tested
tst/unit/test_infra_build_script.py: 77 passed.bump-versioncuts is the real test. Now that the package exists, it should no longer hit the refusal, and the retry covers the next app's first release. I'll watch it.🤖 Generated with Claude Code


Confidence Score: 5/5
This PR appears safe to merge.Summary
Extends GHCR package-linking retries to
docker buildx imagetools create.Reviews (1) · Last reviewed commit: "fix(release): try chromium's first index..." · Reviewed by Greptile