Skip to content

fix(release): chromium's compose is tried again, in fresh stores, while PyPI doesn't list the protocol it just published - #709

Merged
earakely-scale merged 1 commit into
mainfrom
edgararakelyan/fd-5908-compose-retries-pypi
Nov 16, 2026
Merged

earakely-scale merged 1 commit into
mainfrom
edgararakelyan/fd-5908-compose-retries-pypi

Conversation

@earakely-scale

@earakely-scale earakely-scale commented Nov 16, 2026 •

Copy link
Copy Markdown
Collaborator

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 retry tries 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

  • The compose step runs under 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.
  • Tests: the workflow's compose runs under the retry with fresh stores; the retry tries again on the compose's own failure line.

How it was tested

  • tst/unit/test_release_infra_images.py and tst/unit/test_infra_build_script.py: 136 passed.
  • actionlint: no errors (a shellcheck disable=SC2016, since the inner sh expands the single-quoted variables, checked by hand).

bump-version, so its merge cuts the release whose chromium jobs try again.

🤖 Generated with Claude Code

RetriggerView in GreptileConfidence 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.

  • Chromium release composition retries with fresh stores.

Reviews (1) · Last reviewed commit: "fix(release): chromium's compose is trie..." · Reviewed by Greptile

…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
earakely-scale requested a review from a team as a code owner November 16, 2026 18:01
@earakely-scale
earakely-scale merged commit da5dfc9 into main Nov 16, 2026
35 checks passed
@earakely-scale
earakely-scale deleted the edgararakelyan/fd-5908-compose-retries-pypi branch November 16, 2026 18:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant