Repository navigation
ci: read-only Go build mount for CI and release images - #17
Merged
Merged
Conversation
Pull request and tag runs restore the main branch's Go build mount without extracting or writing caches that no other ref can read; the main-branch warmer is the only writer. Module and pnpm mounts are dropped because their layers are already cached. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Release v0.20.0-revised.2 reused PR results (tests skipped) but its image jobs spent ~106s extracting and ~27s exporting tag-scoped caches nobody can read, plus ~47s injecting module/pnpm mounts already covered by layer cache. CI/release now restore only the Go build mount, never write; cache.yaml on main is the single writer.
🤖 Generated with Claude Code