ci(journey): install the Zig ghostty-next names, not a pinned 0.16.0

Merged
TE
1d ago
+24-2

Part of manaflow-ai/cmuxterm-hq#7060. That issue is done when the staging and production Cloud journeys are green twice in a row. Right now the staging journey can't reach any Cloud step.

What broke

#35478 moved ghostty-next to Zig 0.17.0. Two workflows that build Linux cmux-tui from ghostty-next still install a pinned 0.16.0:

  • backend.yml ā†’ journey-staging
  • cloud-journey-pr.yml

So every staging journey since that merge fails at "Build Linux cmux-tui for the headless journey" with ghostty-vt-sys: "Your Zig version v0.16.0 does not meet the required build version of v0.17.0" (run 42031962446, job 127266290172).

Fix

Both workflows now read the Zig version from ghostty-next/build.zig.zon with scripts/ghostty-zig-version.sh (GHOSTTY_ZIG_SOURCE=ghostty-next) and hand that to setup-zig. This is the same pattern #35478 used for cmux-tui-headless-debug.yml, and the form tests/check_ghostty_zig_workflows.py expects. No other workflow still pins version: 0.16.0.

Verification

The journey-staging job on this PR, and on the next feat-cmux-next push after merge, gets past the cmux-tui build.

Changelog

  • CI: the staging Cloud journeys build cmux-tui with the Zig that ghostty-next requires.

Agent session: agent session

šŸ¤– Generated with Claude Code

Autofix with [code]smith
Open in [code]smith Ā· Need help on this PR? Tag @codesmith-bot with what you need.

Summary by cubic

Fixes staging Cloud journeys failing at the cmux-tui build by installing the Zig version ghostty-next requires instead of a pinned 0.16.0. ghostty-next moved to Zig 0.17.0, but backend.yml's journey-staging and cloud-journey-pr.yml still pinned 0.16.0, breaking every staging journey since. Both workflows now resolve the version from ghostty-next/build.zig.zon via scripts/ghostty-zig-version.sh, the same pattern the cmux-tui-headless-debug.yml workflow uses. Part of manaflow-ai/cmuxterm-hq#7060.