cmd/go: conversion from legacy dependency managers puts replacement module path in require section #33406
Labels
help wanted
modules
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
run
go mod init
with 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: