Conversation
Also drops stale golang.org/x/net go.sum entries that were never actually linked into the binary (go.mod-only hashes, no content hash), which Trivy was flagging as a false positive.
go.mod now requires go >= 1.26.3 after the buildkit bump; match it in CI/release so builds use a Go version with current stdlib CVE patches instead of drifting behind on whatever was current at the last release.
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.
Summary
github.com/moby/buildkit(v0.20.2 → v0.33.0) andgolang.org/x/mod(v0.31.0 → v0.41.0), and rungo mod tidyto drop stalegolang.org/x/netgo.sum entries that were never actually linked into the binary (go.mod-only hashes, no content hash) — these were showing up as false-positive Trivy findings.1.24.xto1.26.xto match the newgo.modminimum (buildkit v0.33.0 requires Go ≥1.26.3) and pick up current stdlib CVE patches.Downstream consumers maintain a Trivy suppression list for CVEs baked into prebuilt
dockerfmtbinaries (e.g. https://github.com/gw0/docker-claude-code/blob/main/.trivyignore.yaml). This fixes the root cause upstream instead of relying on per-consumer suppressions.Test plan
go build ./...go vet ./...go test ./...(135 tests pass)