What is the recommended strategy for module authors to upgrade? | Dagger | Page 1

hasty vigil Nov 12, 2024, 11:42 AM

#

As a module author, should I be upgrading my dagger modules when a new version of the Dagger Engine is released. In the dagger.json file there is a reference to the engine version when dagger init or dagger develop was run. If I was to upgrade to 0.14.0 in all of my modules, would it break backwards compatibility? All of my modules are currently at 0.12.5

rich valley Nov 12, 2024, 11:50 AM

#

See if you're using any of the breaking changes in https://github.com/dagger/dagger/releases/tag/v0.13.0

GitHub

Release v0.13.0 · dagger/dagger

v0.13.0 - 2024-09-11
🔥 Breaking Changes

Remove deprecated fields and arguments by @jedevc in #8065

Remove Container.withExec's skipEntrypoint argument - this is now the default (see useEntryp...

#

You're unlikely to be affected by the breaking changes in v0.14.0

hasty vigil Nov 12, 2024, 12:00 PM

#

So upgrading my modules to 0.14.0 doesn't push that dependency down to callers who might be using an older engine version in their own CI setups? What about module authors pulling in one of my modules as a dependency?

#

Thanks for the super fast response btw

#What is the recommended strategy for module authors to upgrade?