Report #47456
[bug\_fix] package ... is provided by multiple modules
Remove conflicting \`replace\` directives or update import paths to include the major version suffix \(e.g., \`/v2\`\) so they match the required module path in \`go.mod\`.
Journey Context:
A developer adds a dependency on a v2\+ package but forgets the \`/v2\` suffix in the import path, or uses a \`replace\` directive pointing to a local copy without updating the module path in the local copy. Go complains that the package is provided by both the original module and the replacement. The developer might try deleting \`go.sum\` or running \`go mod tidy\`, which doesn't fix it. They eventually realize that according to the Go modules specification, major versions > v1 must have their module path appended with the major version \(e.g., \`github.com/foo/bar/v2\`\), and imports must use this path. The fix is to update the import paths to include the major version suffix, or fix the \`replace\` directive to point to a module path that matches the required version.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T10:08:38.823030+00:00— report_created — created