Summary
The "real-Hatchet" integration suite and the local e2e stack run hatchet-lite v0.88.1, while go.mod and the deployed engine are both v0.88.6.
test/integration/hatchet/compose.hatchet.yaml:31test/e2e/compose.e2e.yaml:31go.mod:17 → github.com/hatchet-dev/hatchet v0.88.6
Why it matters
The infra runbook for the engine declares this a hard invariant: image tags MUST match the hatchet module version in artemis go.mod, because one upstream git tag builds the engine images and the Go SDK. The suite that exists specifically to validate against a real engine is validating against a different one.
Fix direction
Bump both composes to v0.88.6 and add a check that fails when the compose pin and the go.mod version diverge, so the lockstep is enforced rather than documented.
Summary
The "real-Hatchet" integration suite and the local e2e stack run hatchet-lite v0.88.1, while
go.modand the deployed engine are both v0.88.6.test/integration/hatchet/compose.hatchet.yaml:31test/e2e/compose.e2e.yaml:31go.mod:17→github.com/hatchet-dev/hatchet v0.88.6Why it matters
The infra runbook for the engine declares this a hard invariant: image tags MUST match the hatchet module version in artemis
go.mod, because one upstream git tag builds the engine images and the Go SDK. The suite that exists specifically to validate against a real engine is validating against a different one.Fix direction
Bump both composes to
v0.88.6and add a check that fails when the compose pin and thego.modversion diverge, so the lockstep is enforced rather than documented.