#Running `gale@v0.0.3` on `dagger@v0.8.1` tag
jovial void
However, this is a low gain task. Not sure if it worth to create issue over it
🙏 , Sorry for screenshot for ants :D. It's a little bit hard to read
wide depot
which workflow is this?
jovial void
test sdk-go
wide depot
jovial void
Yes, exactly
wide depot
OK, so all these workflows depend on https://github.com/dagger/dagger/blob/v0.8.1/internal/mage/go.mod. As you can see, at that tag, the workflow was using dagger.io/dagger v0.7.4 which used to auto-provision v0.6.4. You can see that here: https://github.com/dagger/dagger-go-sdk/blob/v0.7.4/internal/engineconn/version.gen.go
FWIW, we bump the Go SDK version in our internal workflows after we release the Go SDK. Here is the latest PR which bumped to v0.8.4: https://github.com/dagger/dagger/pull/5658 (it's the first commit in the PR that usually does it).
This explains how releasing works, and what happens when: https://github.com/dagger/dagger/blob/main/RELEASING.md
hope that helps!