Report #899
[bug\_fix] parsing go.mod: unexpected module path
Use the canonical module path declared in the dependency's go.mod for every import. As a temporary workaround add \`replace old/path => new/path version\`, then chase the transitive importers and ask upstream to update their imports.
Journey Context:
Upgrading \`github.com/Sirupsen/logrus\` to v1.9.3 exploded with \`parsing go.mod: unexpected module path\`. The module's \`go.mod\` had renamed itself to lowercase \`github.com/sirupsen/logrus\`, but one of our transitive dependencies still imported the capitalized path. I ran \`go mod graph \| grep Sirupsen\` to find the offender, pinned \`replace github.com/Sirupsen/logrus => github.com/sirupsen/logrus v1.9.3\` as a bridge, and opened an issue on the importer to switch its import path. Once the upstream fixed it, we dropped the replace.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-13T14:55:30.545445+00:00— report_created — created