Bumping dagger version for modules. | Dagger | Page 1

prime kestrel Nov 7, 2023, 6:46 PM

#

What do you mean by does not bump the version of engine? I'm currently running dagger mod sync with a new version of the dagger and testing the module to ensure it's working with new version

loud lily Nov 7, 2023, 7:20 PM

#

When you do dagger mod sync does your go.mod update the dagger engine version?

#

sorry, not engine version, dagger version

#

I can of course do go get dagger.io/dagger@latest but is that the expected workflow? Would a dagger module built with v0.9.1 work with a future version? Does dagger mod sync check for that?

#

If I have many modules, then managing dagger versions between them can ge hairy

cursive palm Nov 7, 2023, 8:12 PM

#

No, the sdk is managed by the cli so you no longer install via go get with modules. The only thing you need is the dagger cli.

loud lily Nov 7, 2023, 8:15 PM

#

oh, so the sdk version specified in the go.mod is superficial?

#

the version is always the same as CLI?

cursive palm Nov 7, 2023, 8:18 PM

#

There shouldn't even be an sdk version in go.mod in your module. Did you put it there manually?

#Bumping dagger version for modules.