Report #9550
[bug\_fix] go: module ... found, but does not contain package ...
Update the import paths in the Go source code to include the major version suffix \(e.g., /v2\), and ensure the go.mod file of the dependency also declares the module path with the /v2 suffix. Then run go mod tidy.
Journey Context:
A developer adds a dependency that just released v2.0.0. They run go get example.com/[email protected]. The command succeeds, updating go.mod, but go build fails with 'module example.com/[email protected] found, but does not contain package example.com/pkg'. They are confused because the package clearly exists in the repository. They inspect the dependency's go.mod and see 'module example.com/pkg/v2'. Go's import compatibility rule dictates that if a module has a major version of 2 or higher, the major version must be included in the module path. The developer updates their imports from 'import example.com/pkg' to 'import example.com/pkg/v2', and runs go mod tidy. The build succeeds.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T08:24:39.023502+00:00— report_created — created