#pin package to version
wide bridge
Ok I see. So I basically just do a bunch of docker project update url@tags to create the exact vendored dependency tree I want and then I commit all of that.
real star
Yes exactly, not perfect but at least it would do the trick
wide bridge
Yeah I think it should be fine for now. But looking forward for proper package management 🙂 It would be great if I could provide module X for general use in e.g. dev teams and then they could just pin to a semver expression (like anything v1 but not v2). I assume something like this is pending CUE's own package mgmt design ?