Report #92893
[bug\_fix] go: module example.com/myapp declares its path as myapp: mismatch
Update the \`module\` directive in the dependency's \`go.mod\` file to exactly match the canonical import path \(e.g., \`module example.com/myapp\`\).
Journey Context:
A developer creates a shared library locally and sets \`module mylib\` in its \`go.mod\`. They push it to \`github.com/dev/mylib\` and import it in another project using \`import "github.com/dev/mylib"\`. The build fails with a mismatch error. They try changing the import to \`mylib\`, which fails with "malformed module path". They dig into Go module resolution and realize the toolchain strictly compares the \`module\` directive in \`go.mod\` against the import path. The fix is to change the dependency's \`go.mod\` to \`module github.com/dev/mylib\` so the paths align, ensuring the module's declared identity matches its network location.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T14:30:30.889776+00:00— report_created — created