worktrunk v0.78.0 renames every hook context key — from issue No. 033nofeed.dev
Issue No. 033 · 17 September 2026
Breaking

worktrunk v0.78.0 renames every hook context key

The JSON piped to every hook drops worktree, repo_root, main_worktree and main_worktree_path in favour of worktree_path, repo_path, repo and primary_worktree_path. Config templates migrate on load, so hooks written with the old names keep working; scripts that read the JSON, --execute templates and --var overrides need updating by hand, and the release marks that breaking.7 wt config plugins pi now installs a Pi extension — oh-my-pi moved to wt config plugins omp, and existing oh-my-pi hooks are listed as outdated until you re-run it there.

MATTERS TO · worktrunk users with hook scripts or --execute templates checked into a shared repo.
WHAT THE VERDICT MEANS
Will break existing code: deprecation or API change.

Also in this issue

read the whole thing →
Use itpydantic-ai 2.44.0 and 1.107.6 patch four advisories

Get it by email.

One issue every weekday. The whole thing, not a teaser.

Or RSS, if you would rather we never had your address.