#Updating a module past v0.20.3

1 messages · Page 1 of 1 (latest)

valid acorn
#

hello! I'm having trouble with a module/toolchain of mine past dagger v0.20.3--https://github.com/frantjc/daggerverse/tree/main/dagger-module

it's use is to keep a dagger module using the same version of dagger as you have installed. on v0.20.4, I started seeing:

❯ dagger call bump
▶ ✔ connect 0.2s
✘ load workspace: . 2.7s ERROR
┇ loading type definitions › load module: dagger-module › ModuleSource.asModule(legacyNameOverride: "dagger-module") ›
✘ withExec codegen generate-typedefs --module-source-path /src/dagger-module --module-name dagger-module --introspection-json-path /schema.json --lib-version 7058e9313c720d82c6a07fefb6ce3fab60c7ec4e --output typedefs.json (
  ┆ experimentalPrivilegedNesting: true
  ┆ execMD: "<snip>"
  ) 1.4s ERROR
2026/04/18 22:36:15 INFO generate type definition language=go module-name=dagger-module
2026/04/18 22:36:15 INFO generating go typedefs
2026/04/18 22:36:16 INFO creating directory [skipped] path=.
2026/04/18 22:36:16 INFO writing path=dagger.gen.go
2026/04/18 22:36:16 INFO writing [skipped] path=go.mod
2026/04/18 22:36:16 INFO writing path=go.sum
2026/04/18 22:36:16 INFO creating directory path=internal
2026/04/18 22:36:16 INFO creating directory path=internal/dagger
2026/04/18 22:36:16 INFO writing path=internal/dagger/dagger.gen.go
2026/04/18 22:36:16 INFO writing path=internal/dagger/go.gen.go
2026/04/18 22:36:16 INFO writing path=internal/dagger/wolfi.gen.go
2026/04/18 22:36:16 INFO needs another pass...
starting GOROOT= GOPATH=/go GO111MODULE=off GOPROXY= PWD=. go list -e -f {{context.ReleaseTags}} -- unsafe
starting GOROOT= GOPATH=/go GO111MODULE= GOPROXY= PWD=. go list -f "{{context.GOARCH}} {{context.Compiler}}" -- unsafe
4.553037ms for GOROOT= GOPATH=/go GO111MODULE=off GOPROXY= PWD=. go list -e -f {{context.ReleaseTags}} -- unsafe
starting GOROOT= GOPATH=/go GO111MODULE= GOPROXY= PWD=. go list -e -json=Name,ImportPath,Error,Dir,GoFiles,IgnoredGoFiles,IgnoredOtherFiles,CFile
s,CgoFiles,CXXFiles,MFiles,HFiles,FFiles,SFiles,SwigFiles,SwigCXXFiles,SysoFiles,CompiledGoFiles,DepOnly,Imports,ImportMap,Export,Module -compile
d=true -test=false -export=true -deps=true -find=false -buildvcs=false -pgo=off -- .
5.836064ms for GOROOT= GOPATH=/go GO111MODULE= GOPROXY= PWD=. go list -f "{{context.GOARCH}} {{context.Compiler}}" -- unsafe
82.450212ms for GOROOT= GOPATH=/go GO111MODULE= GOPROXY= PWD=. go list -e -json=Name,ImportPath,Error,Dir,GoFiles,IgnoredGoFiles,IgnoredOtherFile
s,CFiles,CgoFiles,CXXFiles,MFiles,HFiles,FFiles,SFiles,SwigFiles,SwigCXXFiles,SysoFiles,CompiledGoFiles,DepOnly,Imports,ImportMap,Export,Module -
compiled=true -test=false -export=true -deps=true -find=false -buildvcs=false -pgo=off -- .
Error: generate type defs: can only set default path for Object, not VOID_KIND
! exit code: 1

notably, the generated code produced by dagger develop does not seem to include Dagger's core types

repro:

install dagger >= v0.20.4 and

git clone https://github.com/frantjc/daggerverse
cd daggerverse/dagger-module
dagger call bump
#

I tried removing the dependencies on github.com/dagger/dagger, thinking that might be causing the SDK to not generate the core types because it is assuming that they are already available, but that did not seem to help.

deft lynx
valid acorn
#

I forgot to mention, I can reproduce this on 0.20.4, 0.20.5 and 0.20.6

deft lynx
#

if you change the name value of the dagger-module dagger.json an dupdate the calls accordingly, that should work 🙏

deft lynx
valid acorn
#

thanks, I'll give this a shot

deft lynx