Repository navigation
build: Remove redundant Go module downloads - #3346
Merged
EItanya merged 1 commit intoOct 26, 2026
Merged
Conversation
The Go command automatically downloads required modules during ordinary builds. Each build step already mounts the persistent module and compilation caches, so a separate download step does not improve cache reuse. Removing the eager downloads also avoids fetching dependencies that the selected image target does not need. Signed-off-by: timflannagan <timflannagan@gmail.com>
EItanya
approved these changes
Oct 26, 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.
Description
Remove the explicit
go mod downloadsteps from the shared Go, Codex harness,and Claude harness Docker builds. The
go buildcommand automatically downloadsthe modules required by each target, and every build step already mounts the same
BuildKit module and compilation caches.
The separate download vertices therefore do not improve cache reuse. They can
instead fetch dependencies that the selected image target does not need. All three
builder stages continue to resolve their dependencies and build successfully.