Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
What did you do?
Run go build -mod=readonly when an update of go.mod is needed.
What did you expect to see?
A more descriptive error message. Since -mod=readonly is typically supposed to be used in CI, it will save a lot of manual work if the error message did actually tell why an update to go.mod is needed.
E.g.: go: firstname.lastname@example.org requires email@example.com, but go.mod require @v1.2.1 and updates is disabled by -mod=readonly
What did you see instead?
go: updates to go.mod needed, disabled by -mod=readonly
The text was updated successfully, but these errors were encountered:
But since the tool already knows what updates are needed, there is no reason to do it in two steps afaik.
That would require the user to have knowledge of how modules works and what command to run to get the detailed output.