Repository navigation
ci: bump pinned worktrunk to 0.78.0 - #4197
Merged
Merged
Conversation
Three sites: ci.yaml x2, nightly.yaml.
This was referenced Sep 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Weekly CI pin bump for the
worktrunkpin only.=0.77.0→=0.78.0(3 sites:ci.yaml×2,nightly.yaml)This is the
wtthat 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.0declaresrust-version = 1.97, matching the pinned toolchain (rust-toolchain.tomlchannel1.97.0), so it builds underbaptiste0928/cargo-install.Neither of 0.78.0's breaking changes reaches CI. CI calls
wtonly aswt hook pre-merge --yes <filters>(instainci.yamlandnightly.yaml,lockfile doctest docinci.yaml). The hook-context key rename —worktree,repo_root,main_worktree,main_worktree_pathbecomingworktree_path,repo_path,repo,primary_worktree_path— affects templates,--executebodies,--varoverrides, and scripts that read the piped JSON; every[[pre-merge]]entry in.config/wt.tomlis 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. Thewt config plugins pi→ompsplit is a command CI never invokes.Weekly checks that found no drift
1.98.1, so latest−1 is1.97— already whatCargo.toml,tests/helpers/wt-perf/Cargo.toml, andrust-toolchain.tomlpin. Thenightly-2026-08-01pins innightly.yamlare ~7 weeks old, inside the three-month window. No toolchain change, so noflake.lockrefresh (and so the Nix-daemon socket the sandbox blocks never came up).cargo-installpins:cargo-insta1.48.0,cargo-llvm-cov0.9.1,cargo-msrv0.19.3,cargo-udeps0.1.61, andlychee0.24.2 all match their current crates.io release.setup-nu:0.115.1is still the latestnushell/nushellrelease, across all five call sites..codex/cloud.sh's PowerShell7.6.6is still the latestPowerShell/PowerShellrelease and pre-commit4.6.2the latest on PyPI; its Nushell pin trackssetup-nuabove, and its cargo-nextest pin moves in the sibling PR.ubuntu-24.04,macos-26, andwindows-2025each still equal their-latestlabel in theactions/runner-imagesavailability table;ubuntu-24.04-armandmacos-26-intelfollow 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.yamltypescript ignore:npm view @astrojs/check peerDependencies.typescriptis still^5.0.0 || ^6.0.0while the latesttypescriptis7.0.2, so the major-version ignore entry stays (fix(docs): pin typescript to ^6 sonpm ciresolves #3877).claude-haiku-4.5is still the "Fastest" latency row on Anthropic's models page, andgpt-5.6-lunais 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.wt config state logs profilereportssame_context_duplicates: []and 0 extra calls on awt list statusline --format=claude-coderender.WorktreeCreate/WorktreeRemove; its plugin and marketplace entries in that window are consumer-side fixes (installed_plugins.jsoncommit recording, reload-preview extraction,--marketplaceon/plugin install) that leave the published marketplace manifest format alone, and the npm-source--ignore-scriptshardening doesn't apply to a git-sourced marketplace. Gemini CLIv0.60.0hardened extension-loader path resolution and added consent prompts for environment changes;gemini-extension.jsondeclares only name, version, and description — no command paths outside the extension directory and no environment — so neither touches it. Codexrust-v0.155.1and OpenCodev1.18.26–v1.18.31carry nothing affecting the marketplace or the plugins API.