Report #2600
[bug\_fix] go: malformed module path "..."
Change the module path in \`go.mod\` to use all lowercase letters \(e.g., \`module github.com/user/repo\` instead of \`module github.com/User/Repo\`\), and update all import paths accordingly.
Journey Context:
A developer initializes a module using their GitHub username which contains uppercase letters, e.g., \`go mod init github.com/MyUser/MyRepo\`. They write some code and push it. Another developer \(or even the same one on a different machine\) tries to import it via \`go get github.com/MyUser/MyRepo\`. The tooling throws a 'malformed module path' error. The developer is confused because the git repository URL works perfectly fine in the browser. The root cause is that Go module paths are strictly defined to be lowercase to avoid ambiguity in case-insensitive file systems and DNS. The Go tooling enforces this restriction during module resolution. The fix requires changing the \`go.mod\` module directive and all internal imports to lowercase, and releasing a new version.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T13:20:12.126544+00:00— report_created — created