/ go Public
cmd/go: conversion from legacy dependency managers puts replacement module path in require section #33406
help wanted modules NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
What version of Go are you using (
Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (
What did you do?
go mod initwith a dep project that contains source config.
What did you expect to see?
go.mod should put module's old path in require section.
What did you see instead?
go.mod put module's new path in require section.
The text was updated successfully, but these errors were encountered: