#pinning dang

1 messages · Page 1 of 1 (latest)

umbral aurora
#

I cleared my cache and still having the same issue.

#

I also changed github.com/vito/dang/dagger-sdk@main to a completely different repo, e.g. dagger-sdk-doesnt-exist and it still gave me the same build error 😕

wary nexus
#

There was an accidental backwards incompatible change in v0.19.11 that broke dang, so when you go back a few commits you will be running v0.19.11 (your dagger cli) with the older dang. Can just replace that 266e75... commit with d56ca8d99b397a936363bbfaeab1bfef084901d8

I'm not sure about the issue with your pin not changing though, seems like potentially something else (maybe blueprint specific 🤷‍♂️ ). I didn't hit that problem when I bumped all the dang commits. I guess worst case just get rid of the @main for now to get unblocked

umbral aurora
#

Can just replace that 266e75... commit with d56ca8d99b397a936363bbfaeab1bfef084901d8

will that still work with the ./hack/build script?

(because i'm getting the same error with that)

#

get rid of the @main
still the same error

#

I might bail on trying to build an earlier version -- i don't think it's critical in my debugging.