You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sorry - you've got that wrong. The eventual go command integration will adjust (at least during a transition period) based on whether go.mod is present to decide if it's in "versioned mode" or not. But vgo, being named vgo, is always in versioned mode.
The eventual go command integration will adjust (at least during a transition period) based on whether go.mod is present to decide if it's in "versioned mode" or not. But vgo, being named vgo, is always in versioned mode.
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes, per above.
What operating system and processor architecture are you using (
go env
)?What did you do?
At the time of writing,
myitcv.io/immutable
has not been converted to bevgo
aware:in addition to creating a
go.mod
file in the repo root.What did you see?
Got the output:
What did you expect to see?
I was expecting just the regular
go list
behaviour here because there is nogo.mod
(for now).Or have I got that wrong?
The text was updated successfully, but these errors were encountered: