#So, last night (EMEA) my Dagger
1 messages · Page 1 of 1 (latest)
hm, i don't think that should have just started happening - that usually happens from go.mod being a version later than the dagger engine actually supports
dagger v0.11.6 does have a golang version of 1.22.3: https://github.com/dagger/dagger/blob/v0.11.6/ci/consts/versions.go
potentially this is related? but if you're pinning to an old version of the module, this shouldn't be an issue
what's the contents of your dagger.json?
i am confused, the dependency should be pinned