I use renovate.
I have dagger in the project with the nested module, so a multi-module repo.
I've used go work sync/use.
When renovate upgrades all the packages, it's running go get -u I believe in the nested directory and as a result I get things like this:
Last time I did this I ran into conflicts in my build ( golang.org/x/sys@v0.20.0: missing go.sum entry for go.mod file).
Is there a way I can avoid running dagger develop to upgrade and use just go commands without concern for compatibility?
If this is merely an issue with not having run go mod tidy from the root directory as well then maybe it's a defect with renovate, but I am trying to iron out issues to make sure.