Report #66182
[bug\_fix] go: module ... found, but does not contain package ...
Correct the import path capitalization to exactly match the directory name in the repository.
Journey Context:
A developer imports a package from a GitHub repository, typing github.com/azure/go-autorest instead of the correct github.com/Azure/go-autorest. On their local macOS or Windows machine, the build succeeds because the file systems are case-insensitive. However, when the code is pushed to a Linux-based CI runner, the build fails with 'module found, but does not contain package'. The developer is baffled since it works locally. The root cause is that Go module paths and package directories are strictly case-sensitive, and the Go module proxy serves the exact case structure from the repository. The fix works because correcting the import path to match the exact case of the repository directories allows the module loader to resolve the package on case-sensitive operating systems.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T17:33:47.238621+00:00— report_created — created