Repository navigation
ci: bump pinned worktrunk to 0.79.0 - #4298
Merged
Merged
Conversation
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:
worktrunk=0.78.0→=0.79.0, at three sites (ci.yaml×2,nightly.yaml).This is the
wtthat runs the suite (wt hook pre-merge) on all three platforms, so it has its own PR: this PR's CI matrix is the only place the bump gets tested. This week's other drifted pins (cargo-nextest and Nushell) are in their own PRs.Compatibility: worktrunk 0.79.0 declares
rust-version = 1.97, which matches the pinned toolchain (rust-toolchain.tomlchannel1.97.0).Neither of 0.79.0's two breaking changes reaches CI. CI calls
wtonly aswt hook pre-merge --yes <filters>. The breaking changes are towt switch --no-cd -x(the program now runs in the new worktree) and towt merge/wt step rebase, which now pass--no-update-refs. CI invokes none of those commands.Weekly checks that found no drift
1.98.1, so latest−1 is1.97, whichCargo.toml,tests/helpers/wt-perf/Cargo.toml, andrust-toolchain.tomlalready pin. Thenightly-2026-08-01pins innightly.yamlare about 8 weeks old, inside the three-month window. With no toolchain change,flake.lockneeded no refresh.cargo-installpins:cargo-affected0.4.1,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 releases.7.6.6is still the latestPowerShell/PowerShellrelease.cloud.sh's cargo-nextest and Nushell pins move in the sibling PRs.ubuntu-24.04,macos-26, andwindows-2025each still match their-latestlabel in theactions/runner-imagestable, andubuntu-24.04-armandmacos-26-intelfollow those rows. Xcode 27 is still badged preview.dependabot.yamltypescript ignore:@astrojs/checkstill declarestypescript^5.0.0 || ^6.0.0, so the major-version ignore entry stays (fix(docs): pin typescript to ^6 sonpm ciresolves #3877).claude-haiku-4.5is still the current Haiku, andgpt-6-lunais what the Codex models page calls "our most efficient model".wt config state logs profilereportssame_context_duplicates: []on awt list statusline --format=claude-coderender.WorktreeCreate/WorktreeRemovechange. Its newclaude plugin validatechecks (marketplace names it can't install, unquoted${CLAUDE_PLUGIN_ROOT}in shell-form hooks) pass for our manifest: the marketplace and plugin are both namedworktrunk, and every hook quotes"$CLAUDE_PLUGIN_ROOT/...". Codexrust-v0.156.x–0.157.1, Gemini CLIv0.61.0, and OpenCodev1.18.32change nothing in the marketplace, extension, or plugins API.