#dagger v0.16.3 breaks v0.16.2 go modules

1 messages · Page 1 of 1 (latest)

sullen veldt
#

Hello.

Updating the dagger cli made my modules unusable:

dagger -m fooer functions
Error: bootstrap package: existing go.mod has unsupported version 1.24.0 (highest supported version is 1.23.6)                                                             

dagger develop can not solve the problem. It fails also.

dagger -m fooer develop
Error: bootstrap package: existing go.mod has unsupported version 1.24.0 (highest supported version is 1.23.6)
! process "codegen --output /src --module-source-path /src/fooer/dagger --module-name MyModule --introspection-json-path /schema.json" did not complete successfully: exit code: 1
Error: failed to generate code: input: moduleSource.withEngineVersion.generatedContextDirectory failed to run codegen: failed to generate code: failed to get modified source directory for go module sdk codegen: select: process "codegen --output /src --module-source-path /src/fooer/dagger --module-name MyModule --introspection-json-path /schema.json" did not complete successfully: exit code: 1

I had to manually downgrade the go version to go 1.23.6 inside the file go.mod to fix my modules.
This is my repository: https://github.com/chrira/dagger-interfaces/
Anyone having the same issues?

GitHub

Contribute to chrira/dagger-interfaces development by creating an account on GitHub.

hard socket
#

Yep same here

#

I'm using the Python SDK for my modules.

abstract moth
#

sadly, go 1.24 causes pretty massive SIGSEGVs in the engine, so we were forced to downgrade it