This would make it easier to start an upgrade by running go get -e -u ./... and then fixing up the build failures through subsequent code changes (such as adjusting import statements within the main module). That seems like a completely reasonable workflow to me.
A missing dependency currently blocks
go get -ufrom working at all. For a concrete example, see #28424 (comment).
go mod tidyand
go mod vendorhave a
-eflag that means: "attempt to proceed despite errors
encountered while loading packages". I propose that we add an analogous
go get -u.
The text was updated successfully, but these errors were encountered: