release runner was filling its disk - #256
Merged
Merged
Conversation
demigodmode
marked this pull request as ready for review
August 21, 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
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.
The v1.3.1 image job ran the self-hosted runner out of space twice. Failed builds skipped the old cache rotation, so rerunning could not recover.
This clears only workflow-owned Buildx caches and unused builder cache before the build, then cleans partial build data even after a failure. It does not prune containers, images, or volumes. Also checks in the three v1.3.1 workspace version updates that uv regenerated in the lockfile.
Fresh run: 401 passed, 6 skipped. Frontend lint/build and npm audit passed too.