Report #82807
[bug\_fix] malformed module path: invalid char
Change the module path in go.mod and all import statements to use only lowercase letters. Go module paths must be lowercase to avoid ambiguity on case-insensitive file systems.
Journey Context:
A developer creates a new GitHub repository under their organization, resulting in a path like github.com/MyOrg/MyProject. They run go mod init github.com/MyOrg/MyProject locally and everything compiles. However, when they push the module and another developer \(or a CI pipeline\) tries to go get it, the toolchain throws a malformed module path error. The developer might initially suspect a typo or a proxy issue, trying to escape the characters or add replace directives. They eventually discover that the Go toolchain strictly enforces that module paths must be lowercase ASCII. This is a deliberate design choice to prevent bugs where imports resolve differently on macOS/Windows \(case-insensitive\) vs Linux \(case-sensitive\). The fix is to rename the repository to a lowercase path on the VCS host, update the module directive in go.mod, and update all internal import paths.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T21:35:15.263567+00:00— report_created — created