Skip to content

ci: bump pinned worktrunk to 0.78.0 - #4197

Merged
max-sixty merged 1 commit into
mainfrom
weekly/ci-pins-35502216842
Sep 20, 2026
Merged

max-sixty merged 1 commit into
mainfrom
weekly/ci-pins-35502216842

Conversation

@worktrunk-bot

Copy link
Copy Markdown
Collaborator

Weekly CI pin bump for the worktrunk pin only.

  • worktrunk =0.77.0 → =0.78.0 (3 sites: ci.yaml ×2, nightly.yaml)

This is the wt that runs the suite (wt hook pre-merge) on all three platforms, so it goes on its own PR — its own matrix is the only place the bump gets tested. The rest of this week's drift (cargo-affected, cargo-nextest) is in a separate PR.

Compatibility: worktrunk 0.78.0 declares rust-version = 1.97, matching the pinned toolchain (rust-toolchain.toml channel 1.97.0), so it builds under baptiste0928/cargo-install.

Neither of 0.78.0's breaking changes reaches CI. CI calls wt only as wt hook pre-merge --yes <filters> (insta in ci.yaml and nightly.yaml, lockfile doctest doc in ci.yaml). The hook-context key rename — worktree, repo_root, main_worktree, main_worktree_path becoming worktree_path, repo_path, repo, primary_worktree_path — affects templates, --execute bodies, --var overrides, and scripts that read the piped JSON; every [[pre-merge]] entry in .config/wt.toml is a plain string with no template variable, and no CI step pipes the hook context anywhere. The {{ branch }} and {{ target }} variables that the file does use, under [[post-start]], [post-merge] sync, and [list] url, are not in the renamed set and don't run in CI. The wt config plugins pi → omp split is a command CI never invokes.

Weekly checks that found no drift
  • MSRV/toolchain: current stable is 1.98.1, so latest−1 is 1.97 — already what Cargo.toml, tests/helpers/wt-perf/Cargo.toml, and rust-toolchain.toml pin. The nightly-2026-08-01 pins in nightly.yaml are ~7 weeks old, inside the three-month window. No toolchain change, so no flake.lock refresh (and so the Nix-daemon socket the sandbox blocks never came up).
  • Other cargo-install pins: cargo-insta 1.48.0, cargo-llvm-cov 0.9.1, cargo-msrv 0.19.3, cargo-udeps 0.1.61, and lychee 0.24.2 all match their current crates.io release.
  • setup-nu: 0.115.1 is still the latest nushell/nushell release, across all five call sites.
  • Codex Cloud tools: .codex/cloud.sh's PowerShell 7.6.6 is still the latest PowerShell/PowerShell release and pre-commit 4.6.2 the latest on PyPI; its Nushell pin tracks setup-nu above, and its cargo-nextest pin moves in the sibling PR.
  • Runner images: ubuntu-24.04, macos-26, and windows-2025 each still equal their -latest label in the actions/runner-images availability table; ubuntu-24.04-arm and macos-26-intel follow those rows. Ubuntu 26.04 is listed with its own label rather than against -latest, and Xcode 27 is badged preview, so neither is a bump target.
  • dependabot.yaml typescript ignore: npm view @astrojs/check peerDependencies.typescript is still ^5.0.0 || ^6.0.0 while the latest typescript is 7.0.2, so the major-version ignore entry stays (fix(docs): pin typescript to ^6 so npm ci resolves #3877).
  • LLM model pins: claude-haiku-4.5 is still the "Fastest" latency row on Anthropic's models page, and gpt-5.6-luna is still the "lowest cost in the family" entry in the Codex recommended list. GPT-6 Astra sits above it as the most capable model, which doesn't change the commit-generation recommendation.
  • Statusline cache-check: clean. wt config state logs profile reports same_context_duplicates: [] and 0 extra calls on a wt list statusline --format=claude-code render.
  • Agent integration surfaces: nothing to flag. Claude Code shipped 2.1.271–2.1.278 since the last weekly run with no statusline schema additions and no change to WorktreeCreate/WorktreeRemove; its plugin and marketplace entries in that window are consumer-side fixes (installed_plugins.json commit recording, reload-preview extraction, --marketplace on /plugin install) that leave the published marketplace manifest format alone, and the npm-source --ignore-scripts hardening doesn't apply to a git-sourced marketplace. Gemini CLI v0.60.0 hardened extension-loader path resolution and added consent prompts for environment changes; gemini-extension.json declares only name, version, and description — no command paths outside the extension directory and no environment — so neither touches it. Codex rust-v0.155.1 and OpenCode v1.18.26–v1.18.31 carry nothing affecting the marketplace or the plugins API.
  • README date stamp: the blockquote already reads September 2026.
  • Dependency PRs: none open — no Dependabot or renovate PR to review this week.

Three sites: ci.yaml x2, nightly.yaml.
@max-sixty
max-sixty merged commit 172b2e3 into main Sep 20, 2026
42 of 43 checks passed
@max-sixty
max-sixty deleted the weekly/ci-pins-35502216842 branch September 20, 2026 17:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants