SGTM, though I am not sure if I agree. unity still requires cuelang.org/go as a module dependency - what is this gaining for us? I guess you separate the CUE version that we use for the CI and go:generate steps, but I am not sure if that's actually a good idea.
Thanks for catching this. I think I was actually on auto-pilot having made the change in the main CUE repo. There it makes sense because otherwise you have a chicken and egg problem. In this repo that situation does not exist, and the same (stable) CUE version can be used as both a package and tool dependency. I'll drop this from the chain.
Thanks for catching this. I think I was actually on auto-pilot having made the change in the main CUE repo. There it makes sense because otherwise you have a chicken and egg problem. In this repo that situation does not exist, and the same (stable) CUE version can be used as both a package and tool dependency. I'll drop this from the chain.