Draft
Upload toolshed-echo OCI artifacts with a distinct release collector path#4991
Conversation
✅ Deploy Preview for nifty-bassi-e26446 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Co-authored-by: phlax <454682+phlax@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix toolshed-echo upload artifact in Docker workflow
Upload toolshed-echo OCI artifacts with a distinct release collector path
Aug 8, 2026
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.
toolshed-echowas included in the Docker release manifest config, but its OCI tarball was never uploaded from Docker CI, so the release collector had nothing to extract andbuildah manifest addfailed on a missingindex.json. The fix wires the echo tar into the same artifact flow used for release publishing, while avoiding artifact-name collisions with the existing image build job.Root cause
echobuiltdocker/build/oci-output/toolshed-echo-v{echo-version}-{arch}.tarand smoke-tested it, but never uploaded it as a workflow artifact..github/docker-manifests.yml, so publish had no extracted OCI layout to read.Workflow wiring
Upload OCI artifactsto the end of theechojob in.github/workflows/_docker.yml.docker/build/oci-output/*.tar, retention 1 day, fail if missing).Artifact collision handling
buildandechorun in the sameDocker CIworkflow run via thearch × targetmatrix in.github/workflows/docker.yml.upload-artifact@v4+does not merge duplicate artifact names, the echo upload uses a distinct artifact name:oci-debian-echo-${{ inputs.arch }}toolshed-echomanifest entry to match that artifact directory:oci-debian-echo-{arch}/toolshed-echo-v{echo-version}-{arch}.tarArchitecture coverage
echofor bothamd64andarm64, so both tarballs now land in the release collector input set.