wild hinge
I am looking for documentation on how to handle dagger version upgrades when using custom engines.
In my case, engines are self-hosed inside Kubernetes with the Github Actions Kubernetes controller and called from Github Actions via the dagger-for-github action.
At my work we also have a group of private dagger modules that also specify their own version.
Do you have a recommended process for upgrading versions across engine, CLI and modules?
Thanks in advance!
tidal rose
@wild hinge upgrading the engine via our official helm chart should be the most recommended approach since that's mostly what our communit is using
having older clients and/or modules with a newer engine shouldn't be an issue as the engine should be backwards compatible withing the recent versions
wild hinge
Thanks for the quick answer. That was what I was looking for 👍
wild hinge
I gave it a try and ran into some issues that I was able to fix:
I tried to upgrade the engine from v0.16.3 -> v0.17.1 and saw this error:
Error: start session: connect buildkit session: unexpected status 500: incompatible client version v0.16.3
I traced it back to these lines in the engines version.go file: https://github.com/dagger/dagger/blob/v0.17.0/engine/version.go#L32-L38
It looks like from version v0.17.0, the engine expects CLIs to be at least on version v0.17.0 as well. Does not mean we should update the version in Github Actions before custom runners?
