Repository navigation
fix(ci): clean /tmp/digests and guard stale digests in docker-publish (#15184) - #15836
Merged
diegosouzapw merged 1 commit intoOct 10, 2026
Merged
Conversation
Contributor
CI Coverage Report
Coverage artifact was not available for this run. |
3 tasks
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
1 participant
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.
Closes #15184
Root cause
The amd64 build leg can run on the persistent self-hosted
omni-buildrunner.Export digestswrote into a fixed/tmp/digests/*that was never cleaned, so digests from earlier runs were uploaded and the merge job fed all of them toimagetools create, producing N amd64 + 1 arm64 entries in the version index.Fix
Export digests:rm -rf /tmp/digestsbeforemkdir.Guard against stale digestsstep fails if any digest dir holds more than 2 files (amd64 + arm64), before manifests are created.Tests
tests/unit/docker-publish-stale-digests-15184.test.ts(static workflow check). RED on the base (both assertions failed, per the triage plan), GREEN after the fix. Sibling docker-publish tests: 18 pass, 0 fail. Prettier and eslint are clean. actionlint reports only a pre-existing SC2034 warning at a line this PR does not touch.Operator follow-up (not part of this PR): re-publish the
:3.8.51/:latest(+-web/-bun) indexes with only the tag-build digests.