Repository navigation
fix(release): chromium's compose writes its record in a folder of its own, and its first push needn't be answered - #713
Merged
earakely-scale merged 3 commits intoNov 16, 2026
Conversation
… own, and its first push needn't be answered v0.9.1544 composed and probed chromium, then couldn't write its record: Docker had made the folder the local registry's storage is mounted from root's. The folders are made first. And GHCR may refuse a token a package before its first push, so computer-publish takes an index the registry won't say it has as unpublished, with a warning, and creates it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…nners, removed before this merges Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…h passed On GitHub's amd64 and arm64 runners: chromium composed and probed on each, joined as one index in a stand-in for ghcr, the record verified, and an install of a wheel carrying it pulled both arches, resolving and building nothing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
earakely-scale
deleted the
edgararakelyan/fd-5908-release-computer-folders
branch
November 16, 2026 19:18
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.1544's chromium compose resolved, built and probed chromium ready on arm64 (2 min 13 s), then failed writing its record:
PermissionError: ... /home/runner/work/_temp/computers/composed. The registry step mounts$RUNNER_TEMP/computers/registrybefore anything makes it, and Docker makes a missing folder it mounts root's,computers/with it. My VM run had made the folder first, so it never showed.Going over the rest of the jobs for such differences found one more:
computer-publishfails when it can't tell whether the chromium index exists, and GHCR may refuse a token a package before its first push, which this release's is.What changes
computer-buildmakes$RUNNER_TEMP/computers/registryand.../composedbefore it starts the registry.publish-computerstakes an index the registry won't say it has as unpublished, with a warning, and creates it, asinfra_images.pytakes a refused package for the first publish..github/workflows/computers-dry-run.yml, generated fromcomputer-buildaspublish-pypi.ymlhas it, so it runs the release's own steps on GitHub's amd64 and arm64 runners; then the publish step's join andverify-recordwith a local registry on 5001 standing in for ghcr; then an install of a wheel carrying that record composing chromium, which must pull it and resolve and build nothing.How it was tested
tst/unit/test_release_infra_images.pyandtst/unit/test_infra_build_script.py: 138 passed.computer-buildcomposed and probed chromium on amd64 and on arm64, and each wrote its record.verify-recordpassed.bump-version.🤖 Generated with Claude Code


Confidence Score: 5/5
The PR appears safe to merge.Summary
The PR fixes folder ownership before Chromium compose and allows the first publish when GHCR refuses the initial lookup.
Reviews (3) · Last reviewed commit: "ci: remove the temporary dry run of the ..." · Reviewed by Greptile