Also did you call go work sync? I think that might be what I actually use in place of go mod tidy. Sorry, ToTK has been absorbing my free time, so it has been a while since I worked on the audio project where I used workspaces.
https://github.com/golang/go/issues/50750 "*bcmills <https://github.com/bcmills> *commented on Jul 25, 2022 <https://github.com/golang/go/issues/50750#issuecomment-1194322256> go mod tidy is intended to update the module's self-contained dependencies. It doesn't use the workspace because in general one may work on multiple independently-maintained modules in the same workspace, and if you're preparing an upstream commit you definitely don't want that commit to rely on unpublished local modifications. go work sync is intended to update the modules within a workspace to reflect the dependencies selected in that workspace. That is probably what you want if you are working on a set of modules that are all maintained as a single unit." It seems like currently you are basically forced to use 'go work sync' to update dependencies when using workspaces, and not use 'go mod tidy' or a bare 'go get'. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/0acd6b8a-f747-425c-82e6-f2718447bb41n%40googlegroups.com.
