5 ms·
> As I understand it, that's true in the simple case. If you have `my_app -> foo -> bar` then there's only one path to bar, and you only get a new bar when you
by coder543 5y ago
> As I understand it, that's true in the simple case. If you have `my_app -> foo -> bar` then there's only one path to bar, and you only get a new bar when you upgrade foo.
This is not correct. You can update bar independent of foo directly from the top-level go.mod file in your project.
- skybrian 5y agoYes, you can do that by adding a direct dependency on foo. I started by talking about when there isn't a direct dependency on foo. I explicitly talked about having a direct dependency at the end of the second paragraph.
- coder543 5y agoI'm not talking about direct dependencies. Direct and indirect are all listed in the go.mod file. If they aren't listed there, then they aren't in your final binary. If you delete indirect dependencies from the top-level go.mod, your project will fail to compile.