Repository navigation
fix(release): chromium's compose is tried again, in fresh stores, while PyPI doesn't list the protocol it just published - #709
Merged
Conversation
…le PyPI doesn't list the protocol it just published v0.9.1543's arm64 compose resolved agentenv-framework-protocol==0.1.558 39 s after the protocol job published it, before PyPI's index listed it, so the release shipped without composed chromium. The compose now runs under infra_build.py retry, as the image builds do, each try from fresh stores. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
earakely-scale
deleted the
edgararakelyan/fd-5908-compose-retries-pypi
branch
November 16, 2026 18:25
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
v0.9.1543 was the first release to run the chromium jobs #705 added. Its
computer-build (arm64)failed at resolve:No matching distribution found for agentenv-framework-protocol==0.1.558, asked 39 s after the protocol job published it, before PyPI's index listed it. amd64 was cancelled with it (fail-fast), so the release shipped without composed chromium, as these jobs are designed to, and installs compose it as before.The image builds already handle this:
infra_build.py retrytries again after 30, 60 and 120 s while PyPI doesn't list the protocol a build names. The compose didn't run under it.What changes
infra_build.py retry, each try in fresh stores (rm -rf "$XDG_STATE_HOME"), so a try again resolves anew rather than finding the failed pair.How it was tested
tst/unit/test_release_infra_images.pyandtst/unit/test_infra_build_script.py: 136 passed.shellcheck disable=SC2016, since the innershexpands the single-quoted variables, checked by hand).bump-version, so its merge cuts the release whose chromium jobs try again.🤖 Generated with Claude Code


Confidence Score: 5/5
The PR appears safe to merge.Summary
Chromium's release compose now uses the existing retry helper and clears its local stores before each attempt.
Reviews (1) · Last reviewed commit: "fix(release): chromium's compose is trie..." · Reviewed by Greptile