mirror of
https://github.com/max-sixty/worktrunk.git
synced 2026-11-23 01:51:13 +08:00
codex/switch-protect-git-dir
5454
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
5e179374ef |
Protect registered worktrees uniformly from clobbering
Refuse existing destinations inside or containing a checkout or Git store for both explicit and template paths. Keep absent nested destinations valid and remove tracked-entry and case-folding policy. Confirm the primary checkout through Git discovery or a verified parent instead of guessing beside a separate Git store. Fail closed when its location is unknown, and update help and regression coverage. |
||
|
|
f7671175c6 | Read clobber case rules from the owning worktree | ||
|
|
f201a925b6 | Protect tracked symlink entries before clobbering | ||
|
|
71f08b8487 | Merge main and preserve shared clobber protection | ||
|
|
8ee0a70176 |
fix: don't cd into a directory removed before wt exits (#4602)
The shell wrapper acts on the cd directive only after wt exits, and work that runs in between can remove the directory it names. `wt switch -x` writes the directive before starting the program, so a program that removes its own worktree (an agent session that ends with `wt remove`) left the wrapper to `cd` into a missing directory: fish printed `cd: The directory '…' does not exist` and the wrapper returned failure. A hook or alias whose nested `wt switch` targets a worktree that a later step removes hits the same thing. As wt finishes, `finish_command` now reads the directive file and empties it when the directory it names no longer exists, so the shell stays where it started. The outermost wt finishes last, after everything it runs in the foreground, so this one check covers every writer — the `-x` program, hooks, aliases, and nested wt — without touching the five shell wrappers. It is best-effort: if the file can't be read or emptied, the wrapper's own `cd` error still names the directory. One behavior change: a hook that writes a directive naming a path that doesn't exist (a typo, say) used to surface a `cd` error; the shell now stays put silently. `test_concurrent_hooks_log_labels_and_pass_cd_directive` wrote a dummy `CD` target, so it now writes an existing directory. Regression tests cover the `-x` case (`test_switch_execute_that_removes_worktree_withdraws_cd`) and the nested-hook case (`test_directive_to_worktree_removed_by_later_step_is_withdrawn`); both fail without the change. > _This was written by Claude Code on behalf of max-sixty_ --------- Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com> |
||
|
|
057037a69f |
Serialize signal receipt with foreground child admission (#4596)
Ctrl-C during concurrent hook startup could leave `wt` waiting forever after an existing child finished cleanup. If the kernel assigned SIGINT to another thread and delayed its handler, the spawning thread could admit children that missed both the terminal signal and the cancellation checks. Initialize one Unix thread that owns signal receipt and process creation. Other threads inherit blocked SIGINT/SIGTERM; the owner and its children retain the inherited mask. Run foreground admission checks on that owner, preserving cleanup for previously admitted children. Child execution and waits remain concurrent. Library callers that omit early startup initialization retain their existing direct-spawn behavior. Reproduced the failure on both the reported revision and current main by pausing native SIGINT delivery with Linux ptrace: late shell children survived after `CLEANUP_FINISHED`, and `wt` timed out waiting for them. Under the repair, the same pause admitted no additional children and the command exited with 130 after cleanup. This reproduces the reported failure mode; the original CI log alone cannot establish its precise scheduling history. Validation: - Linux project validation: 5,476 tests, pre-commit/Clippy, lockfile, docs, and doctests (one configured skipped test). Two process-group tests required rerunning unchanged with Docker `--init` so orphaned children were reaped. - Regression test delays signal handling while another thread attempts admission; it also checks child masks and reusable commands. Bypassing owner routing makes it fail with “child started before signal receipt finished”; restoring the repair passes. - Native spawn tests cover in-flight TERM cancellation, cancellation overriding an exec failure, and recovery after an owner request panics; both affected tests pass on macOS. - Linux foreground suite: 82 passed, including real bash, zsh, fish, and Nushell jobs. - Paired Linux `wt list` timing: baseline median 21.36 ms, repair 21.28 ms over 20 alternating samples each (nine worktrees, four dirty). Closes #4511. > _This was written by Codex on behalf of max-sixty_ |
||
|
|
bb25aea3ef |
Simplify shell integration detection to known setup lines (#4595)
Shell integration detection used partial shell-syntax heuristics to decide whether an entire rc-file line belonged to Worktrunk. An alias quoting initialization, or an initialization followed by another command, could therefore be removed by uninstall. Recognize complete generated, documented, and historical setup forms instead. Current installer lines come directly from the generator; install, diagnostics, and uninstall share the matcher, which also supplies the shell identity. Preserve custom command names, `.exe` names, Git dispatch, and older installer forms without adding a parser dependency. Remove the syntax-variation heuristics and their tests. Customized shell expressions remain user-managed: uninstall leaves them alone, diagnostics explain that boundary, and installing over such a setup may append the standard initialization line. Regression coverage checks install idempotency and preservation of quoted aliases and compound statements. Validation: shell unit and install/uninstall integration tests, independent CLI lifecycle probes, help snapshots, documentation sync/build, doctests, and all pre-commit checks pass. The full local gate ran 5,430 tests with 5,422 passing. Its documentation-sync failure was resolved by regeneration and a passing repeat; remaining failures were an unchanged startup test, two process-discovery preconditions, and four PowerShell-related failures. The installed `pwsh` also stack-overflows on standalone `1 + 1`, independently of Worktrunk. CI must pass before merge. Closes #4106. > _This was written by Codex on behalf of max-sixty_ |
||
|
|
94338ed210 |
fix: support slash-named remotes in branch inventory (#4271)
Git permits remote names such as `team/fork`. Splitting `team/fork/feature` at its first slash prevented `wt switch feature` from finding the remote branch and misidentified remote names in list and CI consumers. Resolve remote-tracking refs against the longest configured remote prefix once per inventory scan, and retain that boundary through list JSON, CI lookup, and picker deduplication. Read local branches’ upstream remote directly from Git’s tracking metadata. Remote HEAD queries remain supported, and orphaned refs retain the conventional first-segment fallback. Validation: regression reproduction fails with the original parser; 263 focused tests pass, including slash-named and overlapping remotes, remote HEAD queries, and local tracking. Pre-commit/Clippy and documentation checks pass. The full local suite reports 5,316 passes and three PowerShell failures; standalone PowerShell also crashes with “Stack overflow” on this machine. > _This was written by Codex on behalf of max-sixty_ --------- Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com> Co-authored-by: Maximilian Roos <m@maxroos.com> |
||
|
|
7eb2f3ce5e |
fix(shell): configure remaining shells after an rc file error (#4583)
A UTF-16 `.bashrc` stopped the install scan before it reached later shells, leaving PowerShell integration unconfigured. `wt config shell install` now records rc-file errors and continues configuring other shells; it leaves the unreadable file untouched, reports partial failure with a nonzero exit, and identifies a UTF-16 byte-order mark with a re-save hint. The first-run shell prompt also reports a file that becomes unreadable after confirmation. Path-resolution failures still stop the scan, since a missing home blocks every shell and a cancelled PowerShell profile query must stop the command. A regression test with a UTF-16 `.bashrc` and a valid `.zshrc` failed before the change and now confirms zsh installs while Bash remains unchanged. A second test covers an rc file becoming invalid during the first-run prompt. The existing single-shell read-error test also passes. These tests exercise the shared install path on Linux; I have not run the Windows PowerShell profile flow. Closes #4582 — automated triage --------- Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com> |
||
|
|
7a8cacc0eb |
chore: bump the patch group across 1 directory with 11 updates (#4591)
Bumps the patch group with 11 updates in the / directory: | Package | From | To | | --- | --- | --- | | [minijinja](https://github.com/mitsuhiko/minijinja) | `3.0.0` | `3.0.2` | | [serde_json](https://github.com/serde-rs/json) | `1.0.151` | `1.0.154` | | [tree-sitter-highlight](https://github.com/tree-sitter/tree-sitter) | `0.27.0` | `0.27.1` | | [normalize-path](https://github.com/cargo-bins/cargo-binstall) | `0.2.1` | `0.2.2` | | [gix-url](https://github.com/GitoxideLabs/gitoxide) | `0.40.0` | `0.40.1` | | [schemars](https://github.com/GREsau/schemars) | `1.2.2` | `1.2.3` | | [sha2](https://github.com/RustCrypto/hashes) | `0.11.0` | `0.11.1` | | [socket2](https://github.com/rust-lang/socket2) | `0.6.4` | `0.6.5` | | [open](https://github.com/Byron/open-rs) | `5.4.4` | `5.4.5` | | [signal-hook](https://github.com/vorner/signal-hook) | `0.4.4` | `0.4.5` | | [rustix](https://github.com/bytecodealliance/rustix) | `1.1.4` | `1.1.5` | Updates `minijinja` from 3.0.0 to 3.0.2 <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/mitsuhiko/minijinja/blob/main/CHANGELOG.md">minijinja's changelog</a>.</em></p> <blockquote> <h2>3.0.2</h2> <ul> <li>Macros and variables starting with an underscore are now private and are no longer exported from imported templates in Rust and Go, matching Jinja2. They are not visible as attributes of a module imported with <code>{% import %}</code>, and <code>{% from ... import %}</code> of such a name is a syntax error. <code>State::exports</code> / <code>State.Exports</code> no longer return them either, but they can still be retrieved with <code>lookup</code>. <a href="https://redirect.github.com/mitsuhiko/minijinja/issues/970">#970</a></li> <li>Fixed modules imported with <code>{% import %}</code> not being iterable in Go.</li> <li>Fixed the <code>indent</code> filter indenting blank lines of CRLF text when <code>blank</code> is false, in Rust and Go. A blank line ended up as <code>" \r"</code> instead of <code>"\r"</code>, leaving trailing whitespace. <a href="https://redirect.github.com/mitsuhiko/minijinja/issues/972">#972</a></li> <li>Fixed the <code>wordwrap</code> filter ignoring <code>break_long_words</code> when <code>break_on_hyphens</code> is <code>false</code>. The two arguments are independent in Jinja2, so a word longer than <code>width</code> is still broken unless <code>break_long_words</code> is <code>false</code>. <a href="https://redirect.github.com/mitsuhiko/minijinja/issues/940">#940</a></li> <li>Fixed chained integer lookups like <code>foo.1.0</code> failing with a syntax error in Rust and Go. Like in Jinja2, a number right after a dot is now always read as an item index, so <code>foo.1.0</code> is <code>foo[1][0]</code> instead of <code>foo</code> followed by the float <code>1.0</code>. <a href="https://redirect.github.com/mitsuhiko/minijinja/issues/974">#974</a></li> <li>Fixed <code>\x</code> and octal string escapes above <code>\x7f</code> producing invalid UTF-8 in Go. Like in Rust they now produce the code point, so <code>'\xe9'</code> is <code>é</code>. Go now also understands the <code>\b</code> and <code>\f</code> escapes and surrogate pairs written as two <code>\u</code> escapes, and rejects a lone surrogate like Rust does. <a href="https://redirect.github.com/mitsuhiko/minijinja/issues/975">#975</a></li> <li>Added the <code>method</code> argument to the <code>round</code> filter for Jinja2 compatibility in Rust and Go. It takes <code>common</code> (the default), <code>ceil</code> or <code>floor</code>, and both <code>precision</code> and <code>method</code> can now be passed as keyword arguments. Integers are now rounded to a negative precision like in Jinja2, so <code>15|round(-1)</code> is <code>20</code> rather than <code>15</code>. <a href="https://redirect.github.com/mitsuhiko/minijinja/issues/968">#968</a></li> <li>Fixed Python exceptions leaking into later renders in the Python bindings. An exception that MiniJinja did not report, for instance one raised by an iterator after a <code>{% break %}</code>, was raised in place of the next unrelated error. Exceptions are now attached to the error that carries them. Exceptions raised by a loader are also no longer treated as missing templates, so they are no longer ignored by <code>ignore missing</code> or skipped by an include with a list of templates. <a href="https://redirect.github.com/mitsuhiko/minijinja/issues/967">#967</a></li> <li>The Python package is now also published as free-threaded wheels for Linux, macOS and Windows: a version-specific wheel for CPython 3.14t and an <code>abi3t</code> (PEP 803) wheel for CPython 3.15+. <a href="https://redirect.github.com/mitsuhiko/minijinja/issues/969">#969</a></li> <li>The Python package metadata includes the readme again, so the PyPI page shows a project description.</li> </ul> <h2>3.0.1</h2> <ul> <li>The Python package is now also published as Pyodide wheels (PEP 783 <code>pyemscripten</code> platform tag) for Pyodide 0.29 and 314 so it can be installed with <code>micropip</code>.</li> <li>The <code>min</code> and <code>max</code> filters now compare strings case-insensitively by default and accept the <code>case_sensitive</code> and <code>attribute</code> arguments for Jinja2 compatibility in Rust and Go. Previously <code>["b", "P", "n"]|max</code> returned <code>n</code> where Jinja2 returns <code>P</code>, and passing either argument failed with too many arguments.</li> <li>Added the <code>default</code> and <code>base</code> arguments to the <code>int</code> filter and the <code>default</code> argument to the <code>float</code> filter for Jinja2 compatibility in Rust and Go. If a default is given, it is returned for values that cannot be converted and for none instead of failing. In Go both filters now also reject undefined values with strict undefined behavior like in Rust. <a href="https://redirect.github.com/mitsuhiko/minijinja/issues/962">#962</a></li> <li>Fixed the <code>format</code> filter ignoring keyword arguments in Go. Like in Rust they are passed as a trailing mapping and fill <code>%(name)s</code> specs.</li> <li>Fixed whitespace control, <code>lstrip_blocks</code> and the end of line statements in Go only handling ASCII whitespace. Like in Rust they now handle all Unicode whitespace. Syntax errors about unexpected characters now show the character rather than its first byte.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/mitsuhiko/minijinja/commit/a3414f916858c078a720da6ff39fc42bde9eb616"><code>a3414f9</code></a> chore(release): finalize 3.0.2</li> <li><a href="https://github.com/mitsuhiko/minijinja/commit/66fccf269bd088ee39ef804eaa1052321944fffa"><code>66fccf2</code></a> fix(py): include the readme in the package metadata</li> <li><a href="https://github.com/mitsuhiko/minijinja/commit/566e191486c57962296368cff7a6467a3713bfc8"><code>566e191</code></a> chore(py): reformat tests with black 26</li> <li><a href="https://github.com/mitsuhiko/minijinja/commit/e0608e0b2c034d6de7b57c7b8768799a80dd650e"><code>e0608e0</code></a> fix(py): attach Python exceptions to the errors that carry them</li> <li><a href="https://github.com/mitsuhiko/minijinja/commit/529a34c0587862c3fb2817cc0cf106649680a919"><code>529a34c</code></a> feat: add method argument to round (<a href="https://redirect.github.com/mitsuhiko/minijinja/issues/968">#968</a>)</li> <li><a href="https://github.com/mitsuhiko/minijinja/commit/83a10b6097c9b7f2ee6f46760659ced2b5010df7"><code>83a10b6</code></a> fix(go): unescape strings like the Rust lexer (<a href="https://redirect.github.com/mitsuhiko/minijinja/issues/975">#975</a>)</li> <li><a href="https://github.com/mitsuhiko/minijinja/commit/941b883562c3c9a2c2d83748ef04ec796f543d74"><code>941b883</code></a> fix(lexer): read a number after a dot as an item index (<a href="https://redirect.github.com/mitsuhiko/minijinja/issues/974">#974</a>)</li> <li><a href="https://github.com/mitsuhiko/minijinja/commit/cade1a01531c49ee7024dea90d161029335ba31c"><code>cade1a0</code></a> fix(filters): honor break_long_words when break_on_hyphens is false (<a href="https://redirect.github.com/mitsuhiko/minijinja/issues/940">#940</a>)</li> <li><a href="https://github.com/mitsuhiko/minijinja/commit/df9650b8aa5e7a10ed91e43fb3b0a1b1aa5cabe1"><code>df9650b</code></a> fix(filters): don't indent blank CRLF lines in indent (<a href="https://redirect.github.com/mitsuhiko/minijinja/issues/972">#972</a>)</li> <li><a href="https://github.com/mitsuhiko/minijinja/commit/6dae0125e5a124faf22f1307ec964bee70a3ab46"><code>6dae012</code></a> docs: add DuckDB integration to MiniJinja use cases (<a href="https://redirect.github.com/mitsuhiko/minijinja/issues/958">#958</a>)</li> <li>Additional commits viewable in <a href="https://github.com/mitsuhiko/minijinja/compare/minijinja-go/v3.0.0...minijinja-go/v3.0.2">compare view</a></li> </ul> </details> <br /> Updates `serde_json` from 1.0.151 to 1.0.154 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/serde-rs/json/releases">serde_json's releases</a>.</em></p> <blockquote> <h2>v1.0.154</h2> <ul> <li>Support preserve_order in no_std builds (<a href="https://redirect.github.com/serde-rs/json/issues/1333">#1333</a>, thanks <a href="https://github.com/razmser"><code>@razmser</code></a>)</li> </ul> <h2>v1.0.153</h2> <ul> <li>Report invalid UTF-8 at the first bad byte (<a href="https://redirect.github.com/serde-rs/json/issues/1345">#1345</a>, thanks <a href="https://github.com/00200200"><code>@00200200</code></a>)</li> </ul> <h2>v1.0.152</h2> <ul> <li>Preserve sign of <code>-0</code> in arbitrary_precision mode (<a href="https://redirect.github.com/serde-rs/json/issues/1346">#1346</a>, thanks <a href="https://github.com/yuxi-liu-wired"><code>@yuxi-liu-wired</code></a>)</li> <li>Fix comparison of large non-integer values with f32::INFINITY (<a href="https://redirect.github.com/serde-rs/json/issues/1347">#1347</a>, thanks <a href="https://github.com/yuxi-liu-wired"><code>@yuxi-liu-wired</code></a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/serde-rs/json/commit/20572a6d066958542d79cdd6cf1a7cd9f0c8e1f8"><code>20572a6</code></a> Release 1.0.154</li> <li><a href="https://github.com/serde-rs/json/commit/a91bfaf539aa7927ab88086d7a9ff522cb090f7a"><code>a91bfaf</code></a> Fix RandomState links in map documentation</li> <li><a href="https://github.com/serde-rs/json/commit/3c932c05f73bcbc7626db4e1959cbce075d7106e"><code>3c932c0</code></a> Merge pull request <a href="https://redirect.github.com/serde-rs/json/issues/1333">#1333</a> from razmser/no-std-preserve-order</li> <li><a href="https://github.com/serde-rs/json/commit/4b2d7264cef72ef297058ef7d731e7d77574cf3e"><code>4b2d726</code></a> Release 1.0.153</li> <li><a href="https://github.com/serde-rs/json/commit/83335eed01fcfe5f3cfb8064938df935e99e3d61"><code>83335ee</code></a> Touch up PR 1345</li> <li><a href="https://github.com/serde-rs/json/commit/4b4810a451a3095c7bcce792782e460cf1105d8d"><code>4b4810a</code></a> Resolve range_plus_one pedantic clippy lint</li> <li><a href="https://github.com/serde-rs/json/commit/8af71cc0d7ceecd53b9c9b5a9ac512e98d1c78e7"><code>8af71cc</code></a> Merge pull request <a href="https://redirect.github.com/serde-rs/json/issues/1345">#1345</a> from 00200200/fix-invalid-utf8-error-column</li> <li><a href="https://github.com/serde-rs/json/commit/452afa2630f1d568ba06a5f43ad2e2f5303ac000"><code>452afa2</code></a> Correct multiline raw UTF-8 error positions and simplify indexing</li> <li><a href="https://github.com/serde-rs/json/commit/c9f1e3b0216328591262889d9a1c2771f3dd5fff"><code>c9f1e3b</code></a> Release 1.0.152</li> <li><a href="https://github.com/serde-rs/json/commit/854fc70fa3449c302265b75e750401b009b85cd1"><code>854fc70</code></a> Touch up PR 1347</li> <li>Additional commits viewable in <a href="https://github.com/serde-rs/json/compare/v1.0.151...v1.0.154">compare view</a></li> </ul> </details> <br /> Updates `tree-sitter-highlight` from 0.27.0 to 0.27.1 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/tree-sitter/tree-sitter/releases">tree-sitter-highlight's releases</a>.</em></p> <blockquote> <h2>v0.27.1</h2> <h2>What's Changed</h2> <ul> <li>fix: decode UTF-16 surrogate pairs with input endianness by <a href="https://github.com/tree-sitter-ci-bot"><code>@tree-sitter-ci-bot</code></a>[bot] in <a href="https://redirect.github.com/tree-sitter/tree-sitter/pull/5913">tree-sitter/tree-sitter#5913</a></li> <li>fix(cli)!: fix query test capture range matching across lines by <a href="https://github.com/tree-sitter-ci-bot"><code>@tree-sitter-ci-bot</code></a>[bot] in <a href="https://redirect.github.com/tree-sitter/tree-sitter/pull/5918">tree-sitter/tree-sitter#5918</a></li> <li>fix(rust): address new nightly lints by <a href="https://github.com/tree-sitter-ci-bot"><code>@tree-sitter-ci-bot</code></a>[bot] in <a href="https://redirect.github.com/tree-sitter/tree-sitter/pull/5921">tree-sitter/tree-sitter#5921</a></li> <li>fix(generate): resolve token names in debug output by <a href="https://github.com/WillLillis"><code>@WillLillis</code></a> in <a href="https://redirect.github.com/tree-sitter/tree-sitter/pull/5941">tree-sitter/tree-sitter#5941</a></li> <li>fix(generate): keep GCC jump tables enabled for large lexers by <a href="https://github.com/tree-sitter-ci-bot"><code>@tree-sitter-ci-bot</code></a>[bot] in <a href="https://redirect.github.com/tree-sitter/tree-sitter/pull/5985">tree-sitter/tree-sitter#5985</a></li> <li>fix(generate): exclude external word tokens from keyword extraction by <a href="https://github.com/WillLillis"><code>@WillLillis</code></a> in <a href="https://redirect.github.com/tree-sitter/tree-sitter/pull/5989">tree-sitter/tree-sitter#5989</a></li> <li>fix(lib): check shifted stack versions during error recovery by <a href="https://github.com/tree-sitter-ci-bot"><code>@tree-sitter-ci-bot</code></a>[bot] in <a href="https://redirect.github.com/tree-sitter/tree-sitter/pull/5998">tree-sitter/tree-sitter#5998</a></li> <li>fix(generate): detect indirect recursion in flattened productions by <a href="https://github.com/WillLillis"><code>@WillLillis</code></a> in <a href="https://redirect.github.com/tree-sitter/tree-sitter/pull/6003">tree-sitter/tree-sitter#6003</a></li> <li>fix: preserve column dependency when balancing repeat nodes by <a href="https://github.com/tree-sitter-ci-bot"><code>@tree-sitter-ci-bot</code></a>[bot] in <a href="https://redirect.github.com/tree-sitter/tree-sitter/pull/6006">tree-sitter/tree-sitter#6006</a></li> <li>perf(lib): acquire capture lists from a free stack instead of scanning by <a href="https://github.com/tree-sitter-ci-bot"><code>@tree-sitter-ci-bot</code></a>[bot] in <a href="https://redirect.github.com/tree-sitter/tree-sitter/pull/6012">tree-sitter/tree-sitter#6012</a></li> <li>fix(build): don't compile the Wasm stdlib into Emscripten builds by <a href="https://github.com/tree-sitter-ci-bot"><code>@tree-sitter-ci-bot</code></a>[bot] in <a href="https://redirect.github.com/tree-sitter/tree-sitter/pull/6015">tree-sitter/tree-sitter#6015</a></li> <li>fix: various query issues by <a href="https://github.com/tree-sitter-ci-bot"><code>@tree-sitter-ci-bot</code></a>[bot] in <a href="https://redirect.github.com/tree-sitter/tree-sitter/pull/6017">tree-sitter/tree-sitter#6017</a></li> <li>fix(rust): ban <code>std::fs::canonicalize</code> by <a href="https://github.com/tree-sitter-ci-bot"><code>@tree-sitter-ci-bot</code></a>[bot] in <a href="https://redirect.github.com/tree-sitter/tree-sitter/pull/6018">tree-sitter/tree-sitter#6018</a></li> <li>fix(bindings): load Node bindings under Bun again by <a href="https://github.com/tree-sitter-ci-bot"><code>@tree-sitter-ci-bot</code></a>[bot] in <a href="https://redirect.github.com/tree-sitter/tree-sitter/pull/6021">tree-sitter/tree-sitter#6021</a></li> <li>release v0.27.1 by <a href="https://github.com/clason"><code>@clason</code></a> in <a href="https://redirect.github.com/tree-sitter/tree-sitter/pull/6024">tree-sitter/tree-sitter#6024</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/tree-sitter/tree-sitter/compare/v0.27.0...v0.27.1">https://github.com/tree-sitter/tree-sitter/compare/v0.27.0...v0.27.1</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/tree-sitter/tree-sitter/commit/10eb5ac119eec9cb4267a8e035066473983f5f3a"><code>10eb5ac</code></a> release v0.27.1</li> <li><a href="https://github.com/tree-sitter/tree-sitter/commit/1bf93c4f2fd7e95c61ac449d7482ba4b2336a0e6"><code>1bf93c4</code></a> fix(bindings): embed queries in Bun standalone executables</li> <li><a href="https://github.com/tree-sitter/tree-sitter/commit/2173ca8596a71e30526d6cfa965cc7bc32a857be"><code>2173ca8</code></a> fix(bindings): await the load check in the Node binding test</li> <li><a href="https://github.com/tree-sitter/tree-sitter/commit/a89d5b804c3bd51fb5a96b555bc8db25c1b3062c"><code>a89d5b8</code></a> fix(bindings): load Node bindings under Bun again</li> <li><a href="https://github.com/tree-sitter/tree-sitter/commit/17d6c9492cc89c4dff744a9ced04adf3652e3705"><code>17d6c94</code></a> fix(bindings): load <code>node-types.json</code> on Windows</li> <li><a href="https://github.com/tree-sitter/tree-sitter/commit/825b3e4e477ea4bbbe8052c84e61ba8874cf87ae"><code>825b3e4</code></a> fix(rust): ban <code>std::fs::canonicalize</code></li> <li><a href="https://github.com/tree-sitter/tree-sitter/commit/4eb3973da6e202eb720cae5588990ffa42cbbbd0"><code>4eb3973</code></a> fix(web): pass the progress callback to the cursor in <code>Query.captures</code></li> <li><a href="https://github.com/tree-sitter/tree-sitter/commit/60cdb550aeacf6d5479aa3d026864c8d08495910"><code>60cdb55</code></a> fix(test): give the query timeout tests room to time out</li> <li><a href="https://github.com/tree-sitter/tree-sitter/commit/bdf4e7e70d277a3b0681d400d649e2afd84a9f56"><code>bdf4e7e</code></a> fix(lib): charge query cursor work for the states it visits</li> <li><a href="https://github.com/tree-sitter/tree-sitter/commit/dc21d386e8727775197f85128b0d36ac3765b3fb"><code>dc21d38</code></a> fix(lib): halt the query cursor when the progress callback asks to stop</li> <li>Additional commits viewable in <a href="https://github.com/tree-sitter/tree-sitter/compare/v0.27.0...v0.27.1">compare view</a></li> </ul> </details> <br /> Updates `normalize-path` from 0.2.1 to 0.2.2 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/cargo-bins/cargo-binstall/releases">normalize-path's releases</a>.</em></p> <blockquote> <h2>normalize-path-v0.2.2</h2> <h3>Other</h3> <ul> <li>Fix zip extraction to prevent absolute path (<a href="https://redirect.github.com/cargo-bins/cargo-binstall/pull/2685">#2685</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/cargo-bins/cargo-binstall/commit/d17d20fa7d0088cf81f91c59c9453d81f90ee93a"><code>d17d20f</code></a> chore: release (<a href="https://redirect.github.com/cargo-bins/cargo-binstall/issues/2684">#2684</a>)</li> <li><a href="https://github.com/cargo-bins/cargo-binstall/commit/391d1b8d1ed725087f1a90ec2dbca36a26fc8951"><code>391d1b8</code></a> build(deps): bump minisign-verify from 0.2.5 to 0.3.0 in the deps group (<a href="https://redirect.github.com/cargo-bins/cargo-binstall/issues/2690">#2690</a>)</li> <li><a href="https://github.com/cargo-bins/cargo-binstall/commit/218b600ec918a0d3b5e9ed7d208b61ae949fdd0d"><code>218b600</code></a> dep: Upgrade transitive dependencies (<a href="https://redirect.github.com/cargo-bins/cargo-binstall/issues/2689">#2689</a>)</li> <li><a href="https://github.com/cargo-bins/cargo-binstall/commit/d5ebb4e9c17294f73b590ba85824b589533175a1"><code>d5ebb4e</code></a> Fix zip extraction to prevent absolute path (<a href="https://redirect.github.com/cargo-bins/cargo-binstall/issues/2685">#2685</a>)</li> <li><a href="https://github.com/cargo-bins/cargo-binstall/commit/f8162f41a8ea5ec653c5cba967cc1b2d89c867c5"><code>f8162f4</code></a> feat(cli): add --list and --prune to inspect and reconcile manifests (<a href="https://redirect.github.com/cargo-bins/cargo-binstall/issues/2677">#2677</a>)</li> <li><a href="https://github.com/cargo-bins/cargo-binstall/commit/2e63c34ec4f5daa70e042c54ef3144074821c220"><code>2e63c34</code></a> fix: 📌 vergen dep requires MSRV 1.96.0 (<a href="https://redirect.github.com/cargo-bins/cargo-binstall/issues/2683">#2683</a>)</li> <li><a href="https://github.com/cargo-bins/cargo-binstall/commit/ad9eafcdc52590fac666c1abb14d0617f093d7e7"><code>ad9eafc</code></a> docs: add crate author guide for supporting binstall (<a href="https://redirect.github.com/cargo-bins/cargo-binstall/issues/2682">#2682</a>)</li> <li><a href="https://github.com/cargo-bins/cargo-binstall/commit/1b4ce0235b9bdce230e4cb4e537731b8a8789894"><code>1b4ce02</code></a> build(deps): bump mathieudutour/github-tag-action from 6.2 to 7 (<a href="https://redirect.github.com/cargo-bins/cargo-binstall/issues/2678">#2678</a>)</li> <li><a href="https://github.com/cargo-bins/cargo-binstall/commit/6e2f8ea60c0ad3d7ffaaf353706ed5b64facbf17"><code>6e2f8ea</code></a> build(deps): bump taiki-e/install-action from 2.85.3 to 2.87.20 (<a href="https://redirect.github.com/cargo-bins/cargo-binstall/issues/2679">#2679</a>)</li> <li><a href="https://github.com/cargo-bins/cargo-binstall/commit/422f3094be6a0843857aa008b499caaf6bce0da8"><code>422f309</code></a> release: cargo-binstall v1.24.0 (<a href="https://redirect.github.com/cargo-bins/cargo-binstall/issues/2676">#2676</a>)</li> <li>Additional commits viewable in <a href="https://github.com/cargo-bins/cargo-binstall/compare/normalize-path-v0.2.1...normalize-path-v0.2.2">compare view</a></li> </ul> </details> <br /> Updates `gix-url` from 0.40.0 to 0.40.1 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/GitoxideLabs/gitoxide/releases">gix-url's releases</a>.</em></p> <blockquote> <h2>gix-url v0.40.1</h2> <h3>Bug Fixes</h3> <ul> <li> <p>preserve SCP parsing alongside virtual drive prefixes</p> <!-- raw HTML omitted --> <p>The Windows <code>test-fast</code> and fixture suites classified <code>[::1]:repo</code> and <code>[:[@]:...</code> as local paths because their leading <code>[:</code> matched the broad virtual-drive check. They also stopped rejecting an empty helper name in <code>::bar</code>.</p> <p>Require the drive prefix to end at the URL parser's selected colon. This preserves the existing bracket-aware SCP interpretation and empty-helper rejection while retaining digit and Unicode virtual-drive support.</p> </li> </ul> <h3>Commit Statistics</h3> <ul> <li>5 commits contributed to the release over the course of 14 calendar days.</li> <li>14 days passed between releases.</li> <li>1 commit was understood as <a href="https://www.conventionalcommits.org">conventional</a>.</li> <li>0 issues like '(#ID)' were seen in commit messages</li> </ul> <h3>Commit Details</h3> <!-- raw HTML omitted --> <!-- raw HTML omitted --> <ul> <li><strong>Uncategorized</strong> <ul> <li>Merge pull request <a href="https://redirect.github.com/GitoxideLabs/gitoxide/issues/3064">#3064</a> from GitoxideLabs/various-improvements (8c513c5)</li> <li>Preserve SCP parsing alongside virtual drive prefixes (51d280e)</li> <li>Merge pull request <a href="https://redirect.github.com/GitoxideLabs/gitoxide/issues/3053">#3053</a> from GitoxideLabs/various-improvements (2d8dcc4)</li> <li>Release gix-error v0.5.1, gix-utils v0.5.1 (6d1b686)</li> <li>Merge pull request <a href="https://redirect.github.com/GitoxideLabs/gitoxide/issues/3048">#3048</a> from GitoxideLabs/new-release (5fccccf)</li> </ul> </li> </ul> <!-- raw HTML omitted --> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/GitoxideLabs/gitoxide/blob/main/CHANGELOG.md">gix-url's changelog</a>.</em></p> <blockquote> <h1>Changelog</h1> <p>All notable changes to this project will be documented in this file.</p> <p>The format is based on <a href="https://keepachangelog.com/en/1.0.0/">Keep a Changelog</a>, and this project adheres to <a href="https://semver.org/spec/v2.0.0.html">Semantic Versioning</a>.</p> <h2>Unreleased</h2> <p>Headline benefits of this extra-curricular release are various security improvements, and greatly improved error handling and consisstency. Plumbing crates for instance will now use a standard <code>std::error::Error</code> compatible error type.</p> <p>Besides that, the tracing of all commands was greatly improved.</p> <h3>Changed (BREAKING)</h3> <ul> <li> <p><!-- raw HTML omitted --> remove full-screen progress mode</p> <!-- raw HTML omitted --> <p>Full-screen progress required separate command and UI threads plus channel coordination, while line progress already covers long-running commands and works with independently buffered tracing.</p> <p>Remove <code>--progress</code>, <code>--progress-keep-open</code>, and the <code>prodash-render-tui</code> feature. Keep synchronous line progress as the only progress UI.</p> </li> </ul> <h3>New Features</h3> <ul> <li> <p><!-- raw HTML omitted --> make trace output independently configurable</p> <!-- raw HTML omitted --> <p>Quick review only, as it's mostly about tracing and <code>gix</code> which both aren't super important, and are seemingly working well. An extra agent-review couldn't find anything either.</p> <!-- raw HTML omitted --> <p>Replace the old boolean trace switch with a bounded <code>-t</code>/<code>--trace</code> counter: forest INFO and DEBUG at one or two occurrences, then flat DEBUG and TRACE at three or four. Keep <code>--threads</code> long-only and route tracing independently of verbose and progress rendering, including commands with bespoke execution paths and corpus runs.</p> <p>Initialize display tracing once before repository discovery, buffer it outside <code>prodash</code>, and emit it after command and progress teardown. Format forest and flat output with ANSI, then adapt the final stderr write so terminals get color while pipes and <code>NO_COLOR</code> remain plain.</p> <p>Corpus worker subscribers share that sink while retaining their complete JSON trace storage, and flat modes include completed spans. <code>gix tix</code> remains delegated to Tix so it installs only one subscriber.</p> </li> <li> <p><!-- raw HTML omitted --> add and remove linked worktrees from the CLI</p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/GitoxideLabs/gitoxide/commit/dd39fb66e3b1551c9fe849043e39b357a9799ca1"><code>dd39fb6</code></a> Release gix-error v0.5.2, gix-date v0.18.1, gix-actor v0.44.1, gix-trace v0.3...</li> <li><a href="https://github.com/GitoxideLabs/gitoxide/commit/b3248cf099978e0771e7a96b8e7dd26fedb9f9cf"><code>b3248cf</code></a> proof-read (ortho-grammatical)</li> <li><a href="https://github.com/GitoxideLabs/gitoxide/commit/76f8da23d68f0e4da4231425521bfc24e9ba03d7"><code>76f8da2</code></a> Add monthly report for October</li> <li><a href="https://github.com/GitoxideLabs/gitoxide/commit/b8ef9ea94ba69302981c56e16d52b696a00d4c98"><code>b8ef9ea</code></a> Merge pull request <a href="https://redirect.github.com/GitoxideLabs/gitoxide/issues/3082">#3082</a> from 10ne1/sha256-ci-fixes</li> <li><a href="https://github.com/GitoxideLabs/gitoxide/commit/6260a5516e7d604ccf644e714cfb841f7827f2fd"><code>6260a55</code></a> review</li> <li><a href="https://github.com/GitoxideLabs/gitoxide/commit/75ca154086e84a9fee8f87de038ac95e23836570"><code>75ca154</code></a> remove hard-coded SHA-1 from the <code>Commit::short_id()</code> doctest</li> <li><a href="https://github.com/GitoxideLabs/gitoxide/commit/521b3b29ecb227542ef31e1b1971bdac90c76442"><code>521b3b2</code></a> fix: create SHA-256 repositories for <code>object_hash: None</code> in SHA-256-only builds</li> <li><a href="https://github.com/GitoxideLabs/gitoxide/commit/36aaf51e23622f417e9f64aaf8320cb1f54fd536"><code>36aaf51</code></a> make SHA-256-only lib tests really SHA-256-only</li> <li><a href="https://github.com/GitoxideLabs/gitoxide/commit/59ba38b89a4dcaa829f21db437306facbddd7ae7"><code>59ba38b</code></a> Merge pull request <a href="https://redirect.github.com/GitoxideLabs/gitoxide/issues/3080">#3080</a> from cruessler/add-shortcut-for-trivial-myers-changes</li> <li><a href="https://github.com/GitoxideLabs/gitoxide/commit/b7927e6c0160a8c01107cdb3934a595a47b2697e"><code>b7927e6</code></a> review</li> <li>Additional commits viewable in <a href="https://github.com/GitoxideLabs/gitoxide/compare/gix-url-v0.40.0...gix-url-v0.40.1">compare view</a></li> </ul> </details> <br /> Updates `schemars` from 1.2.2 to 1.2.3 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/GREsau/schemars/releases">schemars's releases</a>.</em></p> <blockquote> <h2>v1.2.3</h2> <h3>Fixed</h3> <ul> <li>schema creation panics with arbitrary precision JSON numbers (<a href="https://redirect.github.com/GREsau/schemars/pull/527">GREsau/schemars#527</a>)</li> <li>Resolve <code>unused_qualifications</code> lint violation in generated code (<a href="https://redirect.github.com/GREsau/schemars/issues/539">GREsau/schemars#539</a> / <a href="https://redirect.github.com/GREsau/schemars/pull/541">GREsau/schemars#541</a>)</li> </ul> <h3>Changed</h3> <ul> <li>Put the tag of internally-tagged enums first in the schema's <code>properties</code> array (<a href="https://redirect.github.com/GREsau/schemars/issues/537">GREsau/schemars#537</a> / <a href="https://redirect.github.com/GREsau/schemars/pull/538">GREsau/schemars#538</a>)</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/GREsau/schemars/blob/master/CHANGELOG.md">schemars's changelog</a>.</em></p> <blockquote> <h2>[1.2.3] - 2026-10-12</h2> <h3>Fixed</h3> <ul> <li>schema creation panics with arbitrary precision JSON numbers (<a href="https://redirect.github.com/GREsau/schemars/pull/527">GREsau/schemars#527</a>)</li> <li>Resolve <code>unused_qualifications</code> lint violation in generated code (<a href="https://redirect.github.com/GREsau/schemars/issues/539">GREsau/schemars#539</a> / <a href="https://redirect.github.com/GREsau/schemars/pull/541">GREsau/schemars#541</a>)</li> </ul> <h3>Changed</h3> <ul> <li>Put the tag of internally-tagged enums first in the schema's <code>properties</code> array (<a href="https://redirect.github.com/GREsau/schemars/issues/537">GREsau/schemars#537</a> / <a href="https://redirect.github.com/GREsau/schemars/pull/538">GREsau/schemars#538</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/GREsau/schemars/commit/4791bb7352555d339e45658ca09c092ed9fa1f5d"><code>4791bb7</code></a> v1.2.3</li> <li><a href="https://github.com/GREsau/schemars/commit/c6a89b7ecff45fe8ee26027db5e17ba5859c0476"><code>c6a89b7</code></a> Put the tag of an internally tagged enum first in <code>properties</code></li> <li><a href="https://github.com/GREsau/schemars/commit/c5cd8b5d9aac224be13704bb236677e27703f40f"><code>c5cd8b5</code></a> fix: schema creation panics with arbitrary precision JSON numbers</li> <li><a href="https://github.com/GREsau/schemars/commit/766d70b2d2efab2e047f2cc09fddb15938078223"><code>766d70b</code></a> Resolve <code>unused_qualifications</code> lint in crate and generated code - <a href="https://redirect.github.com/GREsau/schemars/issues/541">#541</a> (<a href="https://redirect.github.com/GREsau/schemars/issues/541">#541</a>)</li> <li><a href="https://github.com/GREsau/schemars/commit/d07655e96fb77f726819ce856db2631d64ce29d6"><code>d07655e</code></a> Resolve clippy error</li> <li>See full diff in <a href="https://github.com/GREsau/schemars/compare/v1.2.2...v1.2.3">compare view</a></li> </ul> </details> <br /> Updates `sha2` from 0.11.0 to 0.11.1 <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/RustCrypto/hashes/commit/138dc5a05b93f8e49cda177fc6cfd7cc43673e5d"><code>138dc5a</code></a> Release sha2 v0.11.1 (<a href="https://redirect.github.com/RustCrypto/hashes/issues/927">#927</a>)</li> <li><a href="https://github.com/RustCrypto/hashes/commit/cf0105661369ca12811082b4fb0904231173c9b6"><code>cf01056</code></a> sha2: fix <code>unsafe_op_in_unsafe_fn</code> lint, bump MSRV to 1.88 (<a href="https://redirect.github.com/RustCrypto/hashes/issues/926">#926</a>)</li> <li><a href="https://github.com/RustCrypto/hashes/commit/7c59cadcfb4cb503fa165e7d43171a61b1378281"><code>7c59cad</code></a> Update Cargo.lock (<a href="https://redirect.github.com/RustCrypto/hashes/issues/921">#921</a>)</li> <li><a href="https://github.com/RustCrypto/hashes/commit/f57b947f978f7ba522df7209a958ba11c426b0d5"><code>f57b947</code></a> streebog: tweak internal implementation (<a href="https://redirect.github.com/RustCrypto/hashes/issues/925">#925</a>)</li> <li><a href="https://github.com/RustCrypto/hashes/commit/336611ffbed10eddafa5f1b9e976120e56a6091d"><code>336611f</code></a> Fix <code>cargo::manual_readme</code> lint (<a href="https://redirect.github.com/RustCrypto/hashes/issues/924">#924</a>)</li> <li><a href="https://github.com/RustCrypto/hashes/commit/1df8877ae0adc264ac561a5a32d6022343d9ceed"><code>1df8877</code></a> md2: fix <code>clippy::needless_range_loop</code> lint (<a href="https://redirect.github.com/RustCrypto/hashes/issues/923">#923</a>)</li> <li><a href="https://github.com/RustCrypto/hashes/commit/6075989cbbd822dbab3ede104c33fcc03645f964"><code>6075989</code></a> sha2: fix loading of round constants on AArch64 backends (<a href="https://redirect.github.com/RustCrypto/hashes/issues/922">#922</a>)</li> <li><a href="https://github.com/RustCrypto/hashes/commit/eadfd90f0dd6272d20530a2cdb69d96319e4a85f"><code>eadfd90</code></a> Update Cargo.lock (<a href="https://redirect.github.com/RustCrypto/hashes/issues/913">#913</a>)</li> <li><a href="https://github.com/RustCrypto/hashes/commit/fa3084083d946ac12436567d5a59c0935d5db1fa"><code>fa30840</code></a> blake2 v0.11.0 (<a href="https://redirect.github.com/RustCrypto/hashes/issues/911">#911</a>)</li> <li><a href="https://github.com/RustCrypto/hashes/commit/f6c786d72ed4d37a32dcd32daa2e7277dd4683e1"><code>f6c786d</code></a> ci: bump the all-deps group across 1 directory with 3 updates (<a href="https://redirect.github.com/RustCrypto/hashes/issues/896">#896</a>)</li> <li>Additional commits viewable in <a href="https://github.com/RustCrypto/hashes/compare/sha2-v0.11.0...sha2-v0.11.1">compare view</a></li> </ul> </details> <br /> Updates `socket2` from 0.6.4 to 0.6.5 <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/rust-lang/socket2/blob/master/CHANGELOG.md">socket2's changelog</a>.</em></p> <blockquote> <h1>0.6.5</h1> <ul> <li>Add support for Emscripten (wasm32) (<a href="https://redirect.github.com/rust-lang/socket2/pull/660">rust-lang/socket2#660</a>).</li> <li>Add support for NuttX (<a href="https://redirect.github.com/rust-lang/socket2/pull/663">rust-lang/socket2#663</a>).</li> <li>Enable <code>Socket::(set_)tos_v4</code> on illumos (<a href="https://redirect.github.com/rust-lang/socket2/pull/662">rust-lang/socket2#662</a>).</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/rust-lang/socket2/commits/v0.6.5">compare view</a></li> </ul> </details> <br /> Updates `open` from 5.4.4 to 5.4.5 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/Byron/open-rs/releases">open's releases</a>.</em></p> <blockquote> <h2>v5.4.5</h2> <h3>Bug Fixes</h3> <ul> <li> <p>check that_detached launchers for immediate failures <code>that_detached()</code> returned as soon as a launcher spawned, so a launcher that failed right after starting was reported as success and no fallback ran.</p> <p>Observe each launcher for 250 ms by delegating to <code>that_detached_with_timeout()</code>. A launcher that exits unsuccessfully within that window falls through to the next candidate; one still running is treated as handed off. The macOS and <code>shellexecute-on-windows</code> paths are unchanged.</p> <p>Extend the fixture tests to call <code>that_detached()</code> directly.</p> </li> <li> <p>restore launcher fallback and support Plasma 6</p> <!-- raw HTML omitted --> <p>When <code>xdg-open</code> starts but exits unsuccessfully, <code>that()</code> and the CLI previously stopped before trying another installed opener. On Plasma 6, the fallback list also omitted the versioned KDE launchers.</p> <h3>Launcher behavior</h3> <ul> <li>Retry reported failures from UNIX desktop launchers and retain the first unsuccessful exit when later candidates are missing.</li> <li>Add <code>kde-open6</code> and <code>kde-open5</code> before the existing <code>kde-open</code> fallback.</li> <li>Keep launcher ordering, argument boundaries, and exit-status policy together so compatibility decisions are explicit.</li> <li>Preserve Windows' stop-on-failure policy and the existing protections for option-shaped and non-UTF-8 paths.</li> </ul> <h3>Bounded detached checks</h3> <p>Add <code>that_detached_with_timeout(path, timeout)</code> to opt into checking the actual launcher status for a configurable interval per candidate. Retry confirmed UNIX launcher failures; consider successful exits or launchers still running at the deadline handed off. A zero timeout polls once.</p> <p>On UNIX, use <code>setsid()</code> while retaining the launcher as a child. Reserve a background waiter before spawning and transfer ownership after a timeout so the launcher can outlive its caller and is eventually reaped. Stop fallback if observing an already-started launcher fails, avoiding a second launch based only on a wait error. Existing detached calls retain their timing behavior. The new API uses command-based launchers on Windows, including when <code>shellexecute-on-windows</code> is enabled.</p> <h3>Historical constraints</h3> <p><code>55dc10d</code> relaxed exit checks for argumentless availability probes, where usage errors are expected. It did not establish that failed real opening operations should stop fallback. <code>245c95e</code> introduced that behavior; the earlier implementation retried unsuccessful operations.</p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/Byron/open-rs/blob/main/changelog.md">open's changelog</a>.</em></p> <blockquote> <h2>5.4.5 (2026-10-22)</h2> <h3>Bug Fixes</h3> <ul> <li> <p><!-- raw HTML omitted --> check that_detached launchers for immediate failures <code>that_detached()</code> returned as soon as a launcher spawned, so a launcher that failed right after starting was reported as success and no fallback ran.</p> <p>Observe each launcher for 250 ms by delegating to <code>that_detached_with_timeout()</code>. A launcher that exits unsuccessfully within that window falls through to the next candidate; one still running is treated as handed off. The macOS and <code>shellexecute-on-windows</code> paths are unchanged.</p> <p>Extend the fixture tests to call <code>that_detached()</code> directly.</p> </li> <li> <p><!-- raw HTML omitted --> restore launcher fallback and support Plasma 6</p> <!-- raw HTML omitted --> <p>When <code>xdg-open</code> starts but exits unsuccessfully, <code>that()</code> and the CLI previously stopped before trying another installed opener. On Plasma 6, the fallback list also omitted the versioned KDE launchers.</p> <h3>Launcher behavior</h3> <ul> <li>Retry reported failures from UNIX desktop launchers and retain the first unsuccessful exit when later candidates are missing.</li> <li>Add <code>kde-open6</code> and <code>kde-open5</code> before the existing <code>kde-open</code> fallback.</li> <li>Keep launcher ordering, argument boundaries, and exit-status policy together so compatibility decisions are explicit.</li> <li>Preserve Windows' stop-on-failure policy and the existing protections for option-shaped and non-UTF-8 paths.</li> </ul> <h3>Bounded detached checks</h3> <p>Add <code>that_detached_with_timeout(path, timeout)</code> to opt into checking the actual launcher status for a configurable interval per candidate. Retry confirmed UNIX launcher failures; consider successful exits or launchers still running at the deadline handed off. A zero timeout polls once.</p> <p>On UNIX, use <code>setsid()</code> while retaining the launcher as a child. Reserve a background waiter before spawning and transfer ownership after a timeout so the launcher can outlive its caller and is eventually reaped. Stop fallback if observing an already-started launcher fails, avoiding a second launch based only on a wait error. Existing detached calls retain their timing behavior. The new API uses command-based launchers on Windows, including when <code>shellexecute-on-windows</code> is enabled.</p> <h3>Historical constraints</h3> <p><code>55dc10d</code> relaxed exit checks for argumentless availability probes, where usage errors are expected. It did not establish that failed real opening operations should stop fallback. <code>245c95e</code> introduced that behavior;</p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/Byron/open-rs/commit/a60a9d508e24417d62e924fb133aaeec0e96f222"><code>a60a9d5</code></a> Release open v5.4.5</li> <li><a href="https://github.com/Byron/open-rs/commit/4e64f6b1ad83b6839e6f2babe657e3897b201daf"><code>4e64f6b</code></a> Merge pull request <a href="https://redirect.github.com/Byron/open-rs/issues/135">#135</a> from Byron/fix-linux-launchers</li> <li><a href="https://github.com/Byron/open-rs/commit/c88759b37476816b89365b2ca9cf614fff999b63"><code>c88759b</code></a> auto-review</li> <li><a href="https://github.com/Byron/open-rs/commit/42a34b073caf7c4ec631ec0657b6ba5387b369f2"><code>42a34b0</code></a> fix(unix): check that_detached launchers for immediate failures</li> <li><a href="https://github.com/Byron/open-rs/commit/279c1b24e34a482f893a09a483294e20f344350b"><code>279c1b2</code></a> fix(unix): restore launcher fallback and support Plasma 6</li> <li>See full diff in <a href="https://github.com/Byron/open-rs/compare/v5.4.4...v5.4.5">compare view</a></li> </ul> </details> <br /> Updates `signal-hook` from 0.4.4 to 0.4.5 <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/vorner/signal-hook/blob/master/CHANGELOG.md">signal-hook's changelog</a>.</em></p> <blockquote> <h1>0.4.5</h1> <ul> <li><code>pipe::register_raw</code> now really sets close-on-exec (<code>FD_CLOEXEC</code>) on the file descriptor, for both pipes and sockets (<a href="https://redirect.github.com/vorner/signal-hook/issues/206">#206</a>).</li> <li>Removed the 32-bit Android <code>sigemptyset</code>/<code>sigaddset</code> fallback, which panicked in <code>emulate_default_handler</code> (<a href="https://redirect.github.com/vorner/signal-hook/issues/207">#207</a>). Android below API 21 is no longer supported.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/vorner/signal-hook/commit/1ee5faa02e1ebb62c38fd9bcfd649afd21bce75e"><code>1ee5faa</code></a> Release 0.4.5</li> <li><a href="https://github.com/vorner/signal-hook/commit/2003e57e9d23bbb0cdd6d9ce49c184fc59ed087e"><code>2003e57</code></a> CI: Check only mio 1.x support on the BSDs</li> <li><a href="https://github.com/vorner/signal-hook/commit/5eaf0844c15a7bc83bb8866ebf9f06f97dbe7a24"><code>5eaf084</code></a> signal-hook-mio: Drop redundant mio 0.7 dev-dependency</li> <li><a href="https://github.com/vorner/signal-hook/commit/f7ceb8ad52137d679459ccf6859a45e9f4a212a4"><code>f7ceb8a</code></a> Use square brackets for vec! in tests</li> <li><a href="https://github.com/vorner/signal-hook/commit/4c1f6f15d79ea1302515a273c067667b3a7be244"><code>4c1f6f1</code></a> CI: Leave out mio 0.6 from BSD checks and doc link check</li> <li><a href="https://github.com/vorner/signal-hook/commit/e52500efd67801fcc3b5eb5cf74264bf46a4a1cd"><code>e52500e</code></a> CI: Make the registry manifest parseable by old cargo</li> <li><a href="https://github.com/vorner/signal-hook/commit/d3f9239fce0289f477b04b34d06157ef51330e29"><code>d3f9239</code></a> Allow deprecated std::isize in the registry</li> <li><a href="https://github.com/vorner/signal-hook/commit/5e09118948b9b66a1674fd98963bac6a7ca932b9"><code>5e09118</code></a> Drop hand-rolled sigset fallback on 32-bit Android</li> <li><a href="https://github.com/vorner/signal-hook/commit/d12e7d9973397a85fe75ca0bc739d7ce01451a7d"><code>d12e7d9</code></a> Set close-on-exec correctly</li> <li>See full diff in <a href="https://github.com/vorner/signal-hook/compare/v0.4.4...v0.4.5">compare view</a></li> </ul> </details> <br /> Updates `rustix` from 1.1.4 to 1.1.5 <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/bytecodealliance/rustix/commit/287214b889865d8e1406a0ee71cc409b6f6191c8"><code>287214b</code></a> chore: Release rustix version 1.1.5</li> <li><a href="https://github.com/bytecodealliance/rustix/commit/0cea1880793a4ec7065498eecc57809e69ae8b20"><code>0cea188</code></a> fix(bug): ns->us overflow handling (<a href="https://redirect.github.com/bytecodealliance/rustix/issues/1655">#1655</a>)</li> <li><a href="https://github.com/bytecodealliance/rustix/commit/a99fd2631a7d513432c47e6fb607581b273db0d2"><code>a99fd26</code></a> build: Remove OUT_DIR probe artifact (<a href="https://redirect.github.com/bytecodealliance/rustix/issues/1628">#1628</a>)</li> <li><a href="https://github.com/bytecodealliance/rustix/commit/1e2954a46ecffa6b30426ad7b1833b226530dcf4"><code>1e2954a</code></a> fix build errors for horizon target (<a href="https://redirect.github.com/bytecodealliance/rustix/issues/1671">#1671</a>)</li> <li><a href="https://github.com/bytecodealliance/rustix/commit/4cecb7240759ed2a561039918bcb360b72ccdec4"><code>4cecb72</code></a> Mangle the name of <code>rustix::runtime</code> to discourage users. (<a href="https://redirect.github.com/bytecodealliance/rustix/issues/1633">#1633</a>)</li> <li><a href="https://github.com/bytecodealliance/rustix/commit/ded795bab5f620ff9fd4045f114f6a14b5bb8e71"><code>ded795b</code></a> Fix compile errors for next libc version (<a href="https://redirect.github.com/bytecodealliance/rustix/issues/1676">#1676</a>)</li> <li><a href="https://github.com/bytecodealliance/rustix/commit/9640071aef0dfd65d21bf01c1dd1baa0a1b13310"><code>9640071</code></a> Expose the <code>O_SYMLINK</code> & <code>O_NOFOLLOW_ANY</code> flags on Apple platforms (<a href="https://redirect.github.com/bytecodealliance/rustix/issues/1666">#1666</a>)</li> <li><a href="https://github.com/bytecodealliance/rustix/commit/cf67411d572468d5fc39e8ac8b4e649ae3e5e9ec"><code>cf67411</code></a> Fix debug printing of abstract socket addrs (<a href="https://redirect.github.com/bytecodealliance/rustix/issues/1615">#1615</a>)</li> <li><a href="https://github.com/bytecodealliance/rustix/commit/aab946409792a9363cbac644c2fd0f7b2762f071"><code>aab9464</code></a> Completely remove <code>rustc_attrs</code>. (<a href="https://redirect.github.com/bytecodealliance/rustix/issues/1663">#1663</a>)</li> <li><a href="https://github.com/bytecodealliance/rustix/commit/a9620e859dbfd92b0a728caa736cdbec78a4b431"><code>a9620e8</code></a> ci: fix syn pin (<a href="https://redirect.github.com/bytecodealliance/rustix/issues/1647">#1647</a>)</li> <li>Additional commits viewable in <a href="https://github.com/bytecodealliance/rustix/compare/v1.1.4...v1.1.5">compare view</a></li> </ul> </details> <br /> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> |
||
|
|
eda83296a8 |
fix(state): keep a var named marker when clearing all markers (#4528)
`wt config state marker clear --all` deleted a user variable named
`marker` along with the markers. A var `marker` is stored at
`worktrunk.state.<branch>.vars.marker`, and the clear matched every key
against `^worktrunk\.state\..+\.marker$`, so `wt config state vars set
marker hello` followed by `marker clear --all` silently removed the var
and reported it as a cleared marker. `wt config state clear --all` hit
the same path. Vars are hand-authored state with no way to regenerate
them.
The clear now skips a `.vars.marker` key unless its value is marker JSON
(`{"marker": "..."}`). Git can't tell the two apart from the key alone:
branch `topic.vars`'s marker has the same key shape as a var `marker` on
branch `topic`. The value check is the same one `all_markers` (used by
`marker list`) already applies, so `--all` clears what the listing shows
as markers.
The new `test_state_clear_marker_all_keeps_var_named_marker` failed
before the fix: it reported `Cleared 3 markers` instead of 2, and the
var was gone. It passes now, along with the other `test_state_clear*`
tests.
Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com>
|
||
|
|
e2e762cb30 |
chore: bump taiki-e/install-action from 2.87.28 to 2.87.31 (#4588)
Bumps [taiki-e/install-action](https://github.com/taiki-e/install-action) from 2.87.28 to 2.87.31. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/taiki-e/install-action/releases">taiki-e/install-action's releases</a>.</em></p> <blockquote> <h2>2.87.31</h2> <ul> <li> <p>Downgrade <code>cargo-sort@latest</code> to 2.1.3.</p> </li> <li> <p>Update <code>vacuum@latest</code> to 0.35.0.</p> </li> <li> <p>Update <code>xh@latest</code> to 0.26.3.</p> </li> <li> <p>Update <code>uv@latest</code> to 0.13.5.</p> </li> <li> <p>Update <code>ubi@latest</code> to 0.13.0.</p> </li> <li> <p>Update <code>trivy@latest</code> to 0.76.1.</p> </li> <li> <p>Update <code>tombi@latest</code> to 1.9.0.</p> </li> <li> <p>Update <code>release-plz@latest</code> to 0.3.174.</p> </li> <li> <p>Update <code>prek@latest</code> to 0.5.7.</p> </li> <li> <p>Update <code>mise@latest</code> to 2026.10.17.</p> </li> <li> <p>Update <code>jaq@latest</code> to 3.1.2.</p> </li> <li> <p>Update <code>espup@latest</code> to 0.17.1.</p> </li> <li> <p>Update <code>cargo-zigbuild@latest</code> to 0.24.0.</p> </li> <li> <p>Update <code>cargo-nextest@latest</code> to 0.9.149.</p> </li> <li> <p>Update <code>biome@latest</code> to 2.6.2.</p> </li> </ul> <h2>2.87.30</h2> <ul> <li> <p>Update <code>zizmor@latest</code> to 1.31.1.</p> </li> <li> <p>Update <code>wasmtime@latest</code> to 50.0.0.</p> </li> <li> <p>Update <code>vacuum@latest</code> to 0.33.2.</p> </li> <li> <p>Update <code>uv@latest</code> to 0.13.4.</p> </li> <li> <p>Update <code>trunk@latest</code> to 0.22.0.</p> </li> <li> <p>Update <code>tombi@latest</code> to 1.8.9.</p> </li> <li> <p>Update <code>syft@latest</code> to 1.55.0.</p> </li> <li> <p>Update <code>release-plz@latest</code> to 0.3.173.</p> </li> <li> <p>Update <code>prek@latest</code> to 0.5.6.</p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/taiki-e/install-action/blob/main/CHANGELOG.md">taiki-e/install-action's changelog</a>.</em></p> <blockquote> <h2>[2.87.31] - 2026-10-23</h2> <ul> <li> <p>Downgrade <code>cargo-sort@latest</code> to 2.1.3.</p> </li> <li> <p>Update <code>vacuum@latest</code> to 0.35.0.</p> </li> <li> <p>Update <code>xh@latest</code> to 0.26.3.</p> </li> <li> <p>Update <code>uv@latest</code> to 0.13.5.</p> </li> <li> <p>Update <code>ubi@latest</code> to 0.13.0.</p> </li> <li> <p>Update <code>trivy@latest</code> to 0.76.1.</p> </li> <li> <p>Update <code>tombi@latest</code> to 1.9.0.</p> </li> <li> <p>Update <code>release-plz@latest</code> to 0.3.174.</p> </li> <li> <p>Update <code>prek@latest</code> to 0.5.7.</p> </li> <li> <p>Update <code>mise@latest</code> to 2026.10.17.</p> </li> <li> <p>Update <code>jaq@latest</code> to 3.1.2.</p> </li> <li> <p>Update <code>espup@latest</code> to 0.17.1.</p> </li> <li> <p>Update <code>cargo-zigbuild@latest</code> to 0.24.0.</p> </li> <li> <p>Update <code>cargo-nextest@latest</code> to 0.9.149.</p> </li> <li> <p>Update <code>biome@latest</code> to 2.6.2.</p> </li> </ul> <h2>[2.87.30] - 2026-10-21</h2> <ul> <li> <p>Update <code>zizmor@latest</code> to 1.31.1.</p> </li> <li> <p>Update <code>wasmtime@latest</code> to 50.0.0.</p> </li> <li> <p>Update <code>vacuum@latest</code> to 0.33.2.</p> </li> <li> <p>Update <code>uv@latest</code> to 0.13.4.</p> </li> <li> <p>Update <code>trunk@latest</code> to 0.22.0.</p> </li> <li> <p>Update <code>tombi@latest</code> to 1.8.9.</p> </li> <li> <p>Update <code>syft@latest</code> to 1.55.0.</p> </li> <li> <p>Update <code>release-plz@latest</code> to 0.3.173.</p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/taiki-e/install-action/commit/1e29709c0ec63babbe8f266397a465f29a825f91"><code>1e29709</code></a> Release 2.87.31</li> <li><a href="https://github.com/taiki-e/install-action/commit/30fbbdf7faf31bb9b916c49edc8cb35a1d69e05e"><code>30fbbdf</code></a> Update <code>cargo-sort@latest</code> to 2.1.3</li> <li><a href="https://github.com/taiki-e/install-action/commit/bce00a3bc1e56e5d9d542062720427927bb19920"><code>bce00a3</code></a> Update <code>vacuum@latest</code> to 0.35.0</li> <li><a href="https://github.com/taiki-e/install-action/commit/dce055e8fcb12572ed99e6d6614fbe75e26f41f3"><code>dce055e</code></a> Update tombi manifest</li> <li><a href="https://github.com/taiki-e/install-action/commit/28b8d620ddfd33eabc70ce00f7bbf78cfb9f4ee7"><code>28b8d62</code></a> Update release-plz manifest</li> <li><a href="https://github.com/taiki-e/install-action/commit/44d13e3166dfcd6732f981cd6047fb9652f3f107"><code>44d13e3</code></a> Update mise manifest</li> <li><a href="https://github.com/taiki-e/install-action/commit/510b77d7d9517935e828cb3d157eceac2acb53f5"><code>510b77d</code></a> Update <code>xh@latest</code> to 0.26.3</li> <li><a href="https://github.com/taiki-e/install-action/commit/601130d9f7cf9a1d9f2b5798216dd7135eb81ae9"><code>601130d</code></a> Update vacuum manifest</li> <li><a href="https://github.com/taiki-e/install-action/commit/8e70b886bfa487f10cbd3bba9ff50a1e6bd9d963"><code>8e70b88</code></a> Update <code>uv@latest</code> to 0.13.5</li> <li><a href="https://github.com/taiki-e/install-action/commit/909288066a7378764b01d5db3f2a2d2e80ece1a2"><code>9092880</code></a> Update <code>ubi@latest</code> to 0.13.0</li> <li>Additional commits viewable in <a href="https://github.com/taiki-e/install-action/compare/v2.87.28...v2.87.31">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> |
||
|
|
f5dec9c4f9 |
fix(push): read the push range from the target branch, not a same-named tag (#4499)
When a tag shares the target branch's name, `wt step push <target>` and `wt merge` compared against the tag instead of the branch. With a tag `main` at the feature commit, both reported "Already up to date with main" and left `refs/heads/main` where it was. This PR makes every range in the push path read the target SHA that `MergeContext::prepare` already snapshots from `refs/heads/<target>`. Git resolves a bare `main` to `refs/tags/main` before `refs/heads/main`. The fast-forward check already used the qualified ref, but four later reads passed the bare name: the commit count, the overlap check against the target worktree's uncommitted changes, the commit graph, and the diffstat. A tag pointing elsewhere also skewed the count, graph, and diffstat shown before the push. Two regression tests in `tests/integration_tests/push.rs` fail on `main` and pass here. One checks that the push advances the branch despite the tag. The other checks that a dirty target worktree's overlapping file is still refused. Before this fix, the overlap went unchecked because the zero commit count made the push a no-op, so nothing was overwritten. Without the zero count, that check would have read an empty range. The existing push and merge tests pass. The exception is `test_merge_no_ff_signs_merge_commit`, which fails identically on unchanged `main` in this sandbox (ssh rejects the signing key's 0644 permissions). <details><summary>Scope</summary> This matches what #694 did for the integration checks (`resolve_preferring_branch`). Other `wt merge` steps that run before the push, such as rebasing onto the target, may take the bare name too. They aren't in this diff. </details> --------- Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com> |
||
|
|
4f71918f1a |
chore: bump clechasseur/rs-cargo from 5.1.0 to 5.1.1 (#4507)
Bumps [clechasseur/rs-cargo](https://github.com/clechasseur/rs-cargo) from 5.1.0 to 5.1.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/clechasseur/rs-cargo/releases">clechasseur/rs-cargo's releases</a>.</em></p> <blockquote> <h2>v5.1.1</h2> <p>Patch version with updated dependencies, including some security fixes.</p> <h2>What's Changed</h2> <ul> <li>fix(deps): update dependency string-argv to ^0.4.0 by <a href="https://github.com/renovate"><code>@renovate</code></a>[bot] in <a href="https://redirect.github.com/clechasseur/rs-cargo/pull/448">clechasseur/rs-cargo#448</a></li> <li>chore(deps-dev): bump handlebars from 4.7.9 to 4.7.10 in the npm_and_yarn group across 1 directory by <a href="https://github.com/dependabot"><code>@dependabot</code></a>[bot] in <a href="https://redirect.github.com/clechasseur/rs-cargo/pull/451">clechasseur/rs-cargo#451</a></li> <li>fix: fix dist, update dependencies, bump version to 5.1.1 by <a href="https://github.com/clechasseur"><code>@clechasseur</code></a> in <a href="https://redirect.github.com/clechasseur/rs-cargo/pull/452">clechasseur/rs-cargo#452</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/clechasseur/rs-cargo/compare/v5.1.0...v5.1.1">https://github.com/clechasseur/rs-cargo/compare/v5.1.0...v5.1.1</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/clechasseur/rs-cargo/commit/62dc8b04d9946cc72018b0c80bd0695ba1f89426"><code>62dc8b0</code></a> fix: fix dist, update dependencies, bump version to 5.1.1 (<a href="https://redirect.github.com/clechasseur/rs-cargo/issues/452">#452</a>)</li> <li><a href="https://github.com/clechasseur/rs-cargo/commit/14ff8fb878ef5dd91b522d175bd5e20cdca9f48c"><code>14ff8fb</code></a> chore(deps-dev): bump handlebars (<a href="https://redirect.github.com/clechasseur/rs-cargo/issues/451">#451</a>)</li> <li><a href="https://github.com/clechasseur/rs-cargo/commit/140ec0b7cca2b543f6b35322e07f65dac97a9ca8"><code>140ec0b</code></a> fix(deps): update dependency string-argv to ^0.4.0 (<a href="https://redirect.github.com/clechasseur/rs-cargo/issues/448">#448</a>)</li> <li><a href="https://github.com/clechasseur/rs-cargo/commit/6f9a668577c648797fc306cf686f02dab4b57b9b"><code>6f9a668</code></a> chore(deps): update actions/upload-artifact action to v7.0.2 (<a href="https://redirect.github.com/clechasseur/rs-cargo/issues/449">#449</a>)</li> <li><a href="https://github.com/clechasseur/rs-cargo/commit/f6fbff6bb68ed95c427a3ccab8b7ce960ce34f39"><code>f6fbff6</code></a> chore(deps): update actions/setup-node action to v7.1.0 (<a href="https://redirect.github.com/clechasseur/rs-cargo/issues/450">#450</a>)</li> <li><a href="https://github.com/clechasseur/rs-cargo/commit/8e3677cdb72ee651e37a009b0337d2027bbb65d1"><code>8e3677c</code></a> chore(deps): update dependency ubuntu to v26 (<a href="https://redirect.github.com/clechasseur/rs-cargo/issues/447">#447</a>)</li> <li><a href="https://github.com/clechasseur/rs-cargo/commit/43f1f475008035596c0cbf3ddd42e65e69d89800"><code>43f1f47</code></a> chore: update README.md</li> <li>See full diff in <a href="https://github.com/clechasseur/rs-cargo/compare/v5.1.0...v5.1.1">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> |
||
|
|
db2641148f |
docs: describe the squash fallback message and detect OpenCode in the skill (#4510)
Two doc claims didn't match the code; this corrects both in their sources and regenerates the mirrors. - **LLM-less fallback** ([`llm-commits.md`](https://github.com/max-sixty/worktrunk/blob/main/docs/src/content/docs/llm-commits.md#fallback-behavior)): the page said every message without an LLM names the changed files. That holds for `wt step commit` ([`src/llm.rs#L744-L767`](https://github.com/max-sixty/worktrunk/blob/de3b9c1c7a03cd6863777668228cfec9ddbb3bfd/src/llm.rs#L744-L767)), but squashes from `wt step squash` and `wt merge` use `Squash commits from <branch>` with the combined subjects in the body ([`src/llm.rs#L883-L889`](https://github.com/max-sixty/worktrunk/blob/de3b9c1c7a03cd6863777668228cfec9ddbb3bfd/src/llm.rs#L883-L889)). The `wt step squash` help already says so. - **Skill tool detection** (`skills/worktrunk/SKILL.md`): the agent was told to run `which claude codex llm aichat`, leaving out `opencode`, which Worktrunk detects itself ([`src/output/commit_generation.rs#L167`](https://github.com/max-sixty/worktrunk/blob/de3b9c1c7a03cd6863777668228cfec9ddbb3bfd/src/output/commit_generation.rs#L167)) and `llm-commits.md` documents. `docs/public/.well-known/agent-skills/index.json` changes only because the SKILL.md digest moved. Verified with `cargo test --test integration test_docs_are_in_sync`; docs-only, so no regression test. --------- Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com> |
||
|
|
9cf6c949e7 |
skills(running-tend): post nightly ci-fix diagnoses on the auto-filed nightly issue (#4512)
When a scheduled nightly fails, `create-issue-on-nightly-failure` opens a `Nightly tests failed` issue before `tend-ci-fix` starts. ci-fix's dedup only searches the bot's `ci-fix:`-titled issues, so it can't see that issue. When ci-fix can't produce a fix for a durable cause, it opens a second, open tracker for the same run. This adds a short `running-tend` section: look up the open `Nightly tests failed` issue by title and post a durable diagnosis there instead of opening a `ci-fix:` tracking issue. A fix PR closes it with `Fixes #<n>`. Transient diagnoses still file their closed `tend-outage` tracker, because ci-fix's repeat-occurrence escalation counts only those. The lookup command in the section returns #4509 today. The fix belongs in the overlay rather than upstream because the auto-filed issue comes from this repo's own `nightly.yaml` job and `.github/nightly-failure.md` template, not from tend. Today's case left two open trackers for one failure. ci-fix [39211195743](https://github.com/max-sixty/worktrunk/actions/runs/39211195743) opened #4511 for nightly run 39206247278, which #4509 already tracked with a triage diagnosis. A second triage run then had to read #4511 as well. The earlier pairs were transient diagnoses, opened and closed within seconds. Those stay as they are, since they are the record the escalation check reads. <details><summary>Occurrences and gate assessment</summary> | Nightly run | Auto-filed issue | ci-fix issue | |---|---|---| | 39206247278 | #4509 (06:39Z) | #4511 (07:17Z), left open | | 32935569443 | #3917 (06:11Z) | #3918 (06:21Z), closed as transient | | 31077344052 | #3751 (07:50Z) | #3752 (08:06Z), closed as transient | | 30519615581 | #3667 (07:37Z) | #3668 (07:40Z), closed as transient | In the 39211195743 session log, the dedup searches were `ci-fix: in:title` (bot-authored), `foreground_jobs in:body` and `startup_interrupt in:body`. #4509's body is only the run link, so none of them matched it. - **Evidence**: High. The same pattern shows up in 4 sessions. Prior review-runs entries on the review-runs tracker #4330 recorded the related triage/ci-fix double diagnosis (#4404, #4476) as cost-only. - **Type**: structural. The search can never match the template's title or body. - **Change**: one targeted new section, which needs 3 or more occurrences and has 4. </details> --------- Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com> |
||
|
|
7427b2faad |
test(picker): wait for rendered rows before the escape-abort snapshot (#4527)
`test_switch_picker_abort_with_escape` failed on Windows in the `affected` run on main ([run 39373658313](https://github.com/max-sixty/worktrunk/actions/runs/39373658313)). Its list snapshot held only the prompt line `>`, with no header and no `@ main` row. The commit that triggered the run (#4516, trash draining) doesn't touch the picker, so this is a test timing race. **Cause.** This is the only capture-before-abort test that passes no inputs (`&[]`). So the only thing that gates its capture is `boot_picker_pty`: it waits for the `> ` prompt, then for the screen to sit unchanged for `STABLE_DURATION` (500ms). Items load asynchronously. On a loaded Windows runner the prompt can stay quiet for 500ms before the first row arrives, and the test captures that frame. **Fix.** Gate the capture on `"has no file changes"`. That preview text appears only after the list has a selected row, so it confirms both panels before the capture. The sibling tests already gate the same way (`&[("", Some("plain-branch"))]`, `&[("", Some("@ main"))]`). If the preview never renders, the test now panics after 30s and shows the screen, instead of producing a snapshot diff. The committed snapshots don't change. **Verification.** All 32 `switch_picker` tests pass locally with `--features shell-integration-tests`. I couldn't reproduce the race on Linux, even under CPU load (0/15 runs on the original code), so the evidence is the code path above plus the failing frame from the run. Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com> |
||
|
|
5acc8da7c5 |
chore: correct stale docs and skill references to the trash drain and picker tabs (#4529)
This PR fixes comments, user docs, and maintainer skills that no longer match the code. There are no behavior changes. #4516 replaced the trash sweep, and several references still describe the old one. A few other docs were wrong before that. - **Troubleshooting, `wt list` timeout example**: the warning prints `TaskKind::display_name()` labels (`working-tree diff, working-tree conflict check`), not the kebab-case names the example showed. The snapshot in `format_drain_timeout_diag`'s tests uses the same labels. - **Troubleshooting, config checklist**: dropped "path must be relative, not absolute". No such validation exists, and `worktree-path` accepts absolute paths. - **`drain_trash` doc** (`src/git/remove.rs`): dropped "Every staged removal starts a drain". That describes the behavior #4516 replaced. Removals now skip spawning when a drain is already running. - **State module doc**: the default-branch override key is `worktrunk.default-branch`, not `worktrunk.default_branch.*`. - **Summary tab number**: `PreviewMode::Summary = 6`, so the `[list] summary` doc comment and a test comment now say tab 6 instead of 5. - **`release` skill**: the safety-scan note named "the trash sweep in `src/commands/process.rs`" as the densest destructive code outside `src/git/`. That sweep now only spawns a drain; the deletion walk is in `src/remove_dir.rs`, so the note points there. `unlinkat`, the walk's primitive, is added to the keyword regex, which would otherwise miss changes to it. - **`writing-user-outputs` skill**: `sweep_stale_trash` is now `run_internal_sweep`. The plugin skills mirror was regenerated, and `test_docs_are_in_sync` and the `switch_picker_dry_run` tests pass. No regression test is needed because no behavior changed. Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com> |
||
|
|
033fbb7e25 |
chore: update tend workflows (0.3.14 → 0.3.15) (#4580)
Regenerate Tend workflows for 0.3.15. Human replies on Tend health issues now reach engagement verification, while bot comments are still filtered before the agent starts. The update also uses the released Tend action and refreshes its pinned uv bootstrap in the generated workflows. The release includes changes to request handling and rate-limit evidence, so the bot can retain outstanding requests and fail explicitly when an activity query is unavailable. See the [0.3.14 to 0.3.15 comparison](https://github.com/max-sixty/tend/compare/0.3.14...0.3.15), especially max-sixty/tend#1559 and max-sixty/tend#1560. Verification: regenerated with Tend 0.3.15 and reviewed the staged workflow diff. The repository's CI checks will validate this PR. Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com> |
||
|
|
224e408b80 |
ci: bump cargo-nextest pin to 0.9.149 (#4586)
Bump the pinned cargo-nextest from 0.9.148 to 0.9.149 in the test and Tend setup actions, coverage workflow, and Codex Cloud setup. The four copies now agree. Version 0.9.149 updates the certificate trust used by `cargo nextest self update`; the release says ordinary test runs do not use that network path. Its crate declares Rust 1.91, below this repository's Rust 1.98 toolchain. Verification: `git diff --check` passed. This pin change needs the PR's CI to exercise test and coverage setup. [Nextest 0.9.149 release notes](https://github.com/nextest-rs/nextest/releases/tag/cargo-nextest-0.9.149) Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com> |
||
|
|
414e8b2c35 |
ci: bump PowerShell and pre-commit pins in the Codex Cloud and web setups (#4500)
Bump the Codex Cloud and web setup PowerShell pins from 7.6.6 to 7.6.8, and the Codex Cloud pre-commit pin from 4.6.2 to 4.7.0. PowerShell 7.6.8 is the current servicing release; its published assets include both setup paths' Linux downloads. Pre-commit 4.7.0 fixes Node hook execution during `commit -a` and in submodules. Verification: `git diff --check` passed, and the upstream release lists both PowerShell assets. These setup paths are outside the GitHub CI jobs, so the PR checks cannot exercise the downloads directly. [PowerShell 7.6.8](https://github.com/PowerShell/PowerShell/releases/tag/v7.6.8) · [pre-commit 4.7.0](https://github.com/pre-commit/pre-commit/releases/tag/v4.7.0) --------- Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com> |
||
|
|
93d7534ea0 |
chore: bump jdx/packslip from 1.7.0 to 1.11.0 (#4590)
Bumps [jdx/packslip](https://github.com/jdx/packslip) from 1.7.0 to 1.11.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/jdx/packslip/releases">jdx/packslip's releases</a>.</em></p> <blockquote> <h2>v1.11.0: Repository-bound signer checks for GitHub and GitLab projects, install fallback, and empty release lists</h2> <p>packslip 1.11.0 makes every verifier in the repository (the CLI, the npm package, and the committable verifier) require a github.com or gitlab.com project to be signed from its own repository. It also makes <code>packslip install</code> fall back to older releases, warn about withdrawn installs, and stop raising some unnecessary trust-change prompts. The format stays at <code>release/v1</code>: the specification changes clarify existing rules, write down how the reference implementations already behave, and settle one conflict between icon rules. No change requires a new format version.</p> <h2>Security</h2> <ul> <li><strong>Identity flags now narrow a forge project's signer policy instead of replacing it</strong> (<a href="https://redirect.github.com/jdx/packslip/issues/256">#256</a>, <a href="https://github.com/jdx"><code>@jdx</code></a>). <code>packslip verify</code> derives a signer policy from a GitHub or GitLab project's name. Before this release, <code>--issuer</code>, <code>--identity</code>, or <code>--identity-prefix</code> replaced that policy. As a result, passing only GitHub Actions' OIDC issuer to <code>--issuer</code> accepted a bundle claiming <code>github.com/owner/tool</code> that any GitHub repository had signed. Now the certificate must also tie the signer to the project's repository. A reusable workflow from another repository still passes when the project's own run called it. Projects on other hosts are unaffected: for them, the flags are still the whole policy.</li> <li><strong>New <code>verify --allow-other-repository</code></strong> accepts a document signed outside the project's repository on purpose, such as a repackager's. You must also pass <code>--issuer</code> and name the signer with <code>--identity</code>, <code>--identity-prefix</code>, or <code>--source-repository</code>. The option is refused with <code>--pubkey</code>. <pre lang="sh"><code>packslip verify packslip.sigstore.json \ --issuer "$GITHUB_OIDC_ISSUER" \ --identity-prefix "$REPACKAGER_WORKFLOW_PREFIX" \ --allow-other-repository </code></pre> The <code>jdx/packslip/releases</code> action gains an <code>allow-other-repository</code> input (default <code>false</code>). It passes the flag automatically when <code>project</code> names a repository other than the one running the action, as with a registry's list.</li> <li><strong>The committable verifier (<code>verifier/packslip-verify.mjs</code>) applies the same repository rule</strong> to a github.com or gitlab.com <code>--project</code> (<a href="https://redirect.github.com/jdx/packslip/issues/258">#258</a>, <a href="https://github.com/jdx"><code>@jdx</code></a>). It also checks the statement's own <code>identity</code> block against the certificate. New failure codes are <code>project-signer</code> and <code>declared-identity</code>, and it has the same <code>--allow-other-repository</code> opt-out (<code>allowOtherRepository</code> in the module). Projects that copied the file must copy the new version to get these checks.</li> <li><strong>The <code>packslip</code> npm package now validates statements and declared signers</strong> (<a href="https://redirect.github.com/jdx/packslip/issues/259">#259</a>, <a href="https://github.com/jdx"><code>@jdx</code></a>). <code>verifyRelease</code> validates the statement against the <code>release/v1</code> rules, which previously let through 14 of 15 conformance reject cases. It checks that <code>predicate.identity</code> names the actual signer and binds a github.com or gitlab.com <code>project</code> to its repository. It throws the new <code>StatementError</code>, <code>DeclaredIdentityError</code>, and <code>ProjectSignerError</code>, and adds the optional <code>allowOtherRepository</code>.</li> <li><strong><code>packslip install</code> now holds a keyless domain project to the repository that first signed it</strong> (<a href="https://redirect.github.com/jdx/packslip/issues/278">#278</a>, <a href="https://github.com/jdx"><code>@jdx</code></a>). Previously, a project named after its host, such as <code>packslip.dev</code>, was matched only by the signer's workflow URL. That let a repository recreated under the old name, or another repository calling the workflow as a reusable workflow, continue as the signer without a prompt. Install now remembers the certificate's repository ID and treats a different or missing ID as a changed signer that needs <code>--accept-trust-change</code>.</li> </ul> <h2>Added</h2> <ul> <li><strong><code>packslip install</code> falls back to older releases</strong> when the latest release has no packslip for this tool or no artifact for this host or <code>--variant</code> (<a href="https://redirect.github.com/jdx/packslip/issues/263">#263</a>, <a href="https://github.com/jdx"><code>@jdx</code></a>). This covers cases such as a monorepo sibling's release whose tag also names this tool's version. Each skipped release produces a warning, for example <code>warning: skipped 3.0.0, GitHub's latest release: its release carries no packslip for github.com/owner/tool</code>. Requests for a version, prefix, or range skip only releases without the tool's packslip. An exact tag tries only that release. Install never falls back after a verification or trust failure, and it stops after 32 fetched bundles and asks for <code>--version</code>. Library users get new <code>discovery</code> APIs: <code>Github::candidates</code>, <code>candidates_with_latest</code>, <code>Candidates</code>, <code>Skipped</code>, and <code>no_packslip</code>.</li> <li><strong><code>packslip install</code> warns when your installed release has been withdrawn</strong> in the project's signed release list (<a href="https://redirect.github.com/jdx/packslip/issues/276">#276</a>, <a href="https://github.com/jdx"><code>@jdx</code></a>). The warning gives the publisher's reason and says whether this run installed a different release: <pre lang="text"><code>warning: the mytool.example.com 1.0.0 you installed was withdrawn in its signed release list: CVE-2026-1234; this run installed 1.1.0 instead </code></pre> </li> <li><strong>Release lists may be empty</strong> (<a href="https://redirect.github.com/jdx/packslip/issues/266">#266</a>, <a href="https://github.com/jdx"><code>@jdx</code></a>). <code>packslip releases</code> without <code>--release</code> writes a list with no releases, and <code>verify</code> and <code>install</code> accept it. A GitHub project can use one to retire every withdrawal, security mark, tag mapping, and <code>latest</code> that earlier lists carried. The releases action still refuses an empty bundle directory.</li> <li><strong>GitHub and GitLab repository names match in any case</strong> (<a href="https://redirect.github.com/jdx/packslip/issues/265">#265</a>, <a href="https://github.com/jdx"><code>@jdx</code></a>), as those forges treat them. For example, <code>install jqlang/JQ</code> now finds jq's <code>jq-1.7.1</code> tags, and an identity prefix spelled <code>JDX/HK</code> matches a certificate from <code>jdx/hk</code>. Monorepo subpaths, workflow paths and refs, and names on other hosts still compare exactly. Repository IDs still pin identity. A <code>pins.d</code> file with two entries for one project that differ only in case is refused.</li> <li><strong>Documented <code>variant</code> spellings for soft-float and CPU-level builds, plus Go helpers</strong> (<a href="https://redirect.github.com/jdx/packslip/issues/277">#277</a>, <a href="https://github.com/jdx"><code>@jdx</code></a>). <code>softfloat</code> marks a soft-float 386, ARM, or MIPS build. A CPU level above the platform default uses the toolchain's name, such as <code>v3</code> or <code>v8.2-lse</code>. The Go module adds <code>VariantFromGo</code> and <code>VariantFromRustABI</code>: <pre lang="go"><code>packslip.VariantFromGo("amd64", "v3") // "v3" packslip.VariantFromRustABI("gnueabi") // "softfloat" </code></pre> </li> </ul> <h2>Fixed</h2> <ul> <li> <p><strong><code>packslip verify</code> and <code>packslip pin</code> without trust flags accept a release signed through another repository's reusable workflow</strong>, as <code>install</code> has since 1.7.0 (<a href="https://redirect.github.com/jdx/packslip/issues/257">#257</a>, <a href="https://github.com/jdx"><code>@jdx</code></a>). For example, mkghtag 0.1.14-10 is signed through <code>suzuki-shunsuke/go-release-workflow</code>. It installed but failed <code>verify</code> and <code>pin</code>; it now passes both.</p> </li> <li> <p><strong><code>install</code> no longer asks for <code>--accept-trust-change</code> when a release retires a build, retires a format, or renames a command</strong> (<a href="https://redirect.github.com/jdx/packslip/issues/262">#262</a>, <a href="https://github.com/jdx"><code>@jdx</code></a>). Provenance links are now compared only for builds that both releases offer. A shared build that loses links still triggers a prompt.</p> </li> <li> <p><strong><code>--version 1.2.3</code> now selects a release versioned <code>1.2.3+build.5</code></strong> (<a href="https://redirect.github.com/jdx/packslip/issues/264">#264</a>, <a href="https://github.com/jdx"><code>@jdx</code></a>). Tag parsing also tries every allowed prefix in order, so <code>tool-suite-1.2.0</code> names 1.2.0 for <code>github.com/acme/tool-suite/tool</code>. A tag that a signed list maps to another version no longer also offers the version derived from the tag.</p> </li> <li> <p><strong><code>packslip create</code> writes <code>published_at</code> in UTC</strong> when given another offset (<a href="https://redirect.github.com/jdx/packslip/issues/267">#267</a>, <a href="https://github.com/jdx"><code>@jdx</code></a>). <code>packslip releases</code> and the Go library also write their timestamps in UTC with <code>Z</code>. Consumers still accept any RFC 3339 offset.</p> </li> <li> <p><strong><code>packslip create</code> refuses an <code>os_min</code> or <code>glibc_min</code> that is not a version number</strong>, such as <code>glibc-2.31</code> (<a href="https://redirect.github.com/jdx/packslip/issues/268">#268</a>, <a href="https://github.com/jdx"><code>@jdx</code></a>). The Go publisher's <code>Build</code> refuses it too. Already-published packslips with such values still verify.</p> </li> <li> <p><strong>Icon resources at several hicolor sizes are all selected</strong> (<a href="https://redirect.github.com/jdx/packslip/issues/270">#270</a>, <a href="https://github.com/jdx"><code>@jdx</code></a>). Previously, a more specific entry hid the others. The hicolor size directory is now part of an icon's identity.</p> </li> <li> <p><strong>Malformed statements are refused consistently</strong> (<a href="https://redirect.github.com/jdx/packslip/issues/260">#260</a>, <a href="https://github.com/jdx"><code>@jdx</code></a>). The CLI and Rust library now refuse three shapes that the Go module and npm package already refused:</p> <ul> <li>an object written as an array of its field values</li> <li>a <code>bin</code> entry with an empty command name, such as the path <code>"tool/"</code></li> <li>a <code>sigstore-oidc</code> identity with an empty <code>key_id</code> or a missing or empty <code>issuer</code></li> </ul> <p>Statements that don't fit the model now report <code>statement is not well-formed</code> instead of "not valid JSON".</p> </li> <li> <p><strong><code>packslip install</code> calls the <code>ps1_…</code> value a "signer fingerprint"</strong> in its output and errors (<a href="https://redirect.github.com/jdx/packslip/issues/271">#271</a>, <a href="https://github.com/jdx"><code>@jdx</code></a>), matching <code>packslip pin</code> and <code>--pin</code>. Success output now prints <code>Signer fingerprint:</code> instead of <code>Signer pin:</code>. Install also no longer panics if stdout is closed after an install.</p> </li> </ul> <h2>Specification</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/jdx/packslip/blob/main/CHANGELOG.md">jdx/packslip's changelog</a>.</em></p> <blockquote> <h1>Changelog</h1> <h2><a href="https://github.com/jdx/packslip/compare/v1.11.0..v1.11.1">1.11.1</a> - 2026-10-24</h2> <h3>📦️ Dependency Updates</h3> <ul> <li>update mise tools by <a href="https://github.com/renovate%5Bbot%5D"><code>@renovate[bot]</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/289">#289</a></li> <li>update sigstore to 0.15 and lzma-rust2 to 0.22 by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/295">#295</a></li> <li>update rust crate zip to v9 by <a href="https://github.com/renovate%5Bbot%5D"><code>@renovate[bot]</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/293">#293</a></li> <li>update dependency hk to latest by <a href="https://github.com/renovate%5Bbot%5D"><code>@renovate[bot]</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/296">#296</a></li> <li>update rust crate usage_rs to v7.1.2 by <a href="https://github.com/renovate%5Bbot%5D"><code>@renovate[bot]</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/300">#300</a></li> </ul> <!-- raw HTML omitted --> <h2><a href="https://github.com/jdx/packslip/compare/v1.10.1..v1.11.0">1.11.0</a> - 2026-10-23</h2> <h3>🚀 Features</h3> <ul> <li><strong>(forge)</strong> match GitHub and GitLab repository names in any case by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/265">#265</a></li> <li><strong>(go)</strong> document softfloat and CPU-level variants and add Go helpers by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/277">#277</a></li> <li><strong>(install)</strong> warn when the installed release has been withdrawn by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/276">#276</a></li> <li><strong>(install)</strong> skip releases without this tool's packslip or a host artifact by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/263">#263</a></li> <li><strong>(releases)</strong> build and accept a release list with no releases by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/266">#266</a></li> </ul> <h3>🐛 Bug Fixes</h3> <ul> <li><strong>(create)</strong> refuse an os_min or glibc_min that is not a version number by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/268">#268</a></li> <li><strong>(discovery)</strong> let --version 1.2.3 select 1.2.3+build.5 and try every tag prefix by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/264">#264</a></li> <li><strong>(install)</strong> flag dropped provenance only on builds both releases offer by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/262">#262</a></li> <li><strong>(install)</strong> call the ps1_ value a signer fingerprint in output and errors by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/271">#271</a></li> <li><strong>(install)</strong> hold a keyless domain project to the repository that signed it first by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/278">#278</a></li> <li><strong>(resources)</strong> install every hicolor size of an icon by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/270">#270</a></li> <li><strong>(verify)</strong> accept a release signed through another repository's reusable workflow by default by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/257">#257</a></li> <li>refuse array-form objects, empty bin names, and incomplete keyless identities by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/260">#260</a></li> <li>write published_at in UTC when given another offset by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/267">#267</a></li> </ul> <h3>📚 Documentation</h3> <ul> <li><strong>(cli)</strong> rewrite command help and the CLI reference by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/282">#282</a></li> <li><strong>(skill)</strong> rewrite the packslip agent skill as concise directives by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/284">#284</a></li> <li><strong>(spec)</strong> rewrite the specification for clarity without changing its rules by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/281">#281</a></li> <li>add a generated GitHub Actions reference and keep old section links working by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/279">#279</a></li> <li>rewrite the guides around publishing, installing, and verifying by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/280">#280</a></li> <li>rewrite the README and the contributor, release, and security guides by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/283">#283</a></li> </ul> <h3>🛡️ Security</h3> <ul> <li><strong>(verify)</strong> make identity flags narrow a GitHub or GitLab project's signer policy by <a href="https://github.com/jdx"><code>@jdx</code></a> in <a href="https://redirect.github.com/jdx/packslip/pull/256">#256</a></li> </ul> <h3>🔍 Other Changes</h3> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/jdx/packslip/commit/ddcddd9c8c33977d2d08d5db91caec579da59aab"><code>ddcddd9</code></a> chore: release v1.11.0 (<a href="https://redirect.github.com/jdx/packslip/issues/286">#286</a>)</li> <li><a href="https://github.com/jdx/packslip/commit/0c37e0997281c43d88e85ea10a7e580248dca5fd"><code>0c37e09</code></a> feat(go): document softfloat and CPU-level variants and add Go helpers (<a href="https://redirect.github.com/jdx/packslip/issues/277">#277</a>)</li> <li><a href="https://github.com/jdx/packslip/commit/133e7b6d647ee1c9c969df35d3fcf20f1d275b7a"><code>133e7b6</code></a> docs(skill): rewrite the packslip agent skill as concise directives (<a href="https://redirect.github.com/jdx/packslip/issues/284">#284</a>)</li> <li><a href="https://github.com/jdx/packslip/commit/de69c3a60ae091ae7a6e7e4fde2120e05dcb8dfa"><code>de69c3a</code></a> docs: rewrite the README and the contributor, release, and security guides (#...</li> <li><a href="https://github.com/jdx/packslip/commit/8bbb7aa875399ae0780c4e8dc65510626fc85657"><code>8bbb7aa</code></a> docs(cli): rewrite command help and the CLI reference (<a href="https://redirect.github.com/jdx/packslip/issues/282">#282</a>)</li> <li><a href="https://github.com/jdx/packslip/commit/b0681413763cb8d2faf31654e888e465bd90631c"><code>b068141</code></a> docs(spec): rewrite the specification for clarity without changing its rules ...</li> <li><a href="https://github.com/jdx/packslip/commit/53317ad64f80b685f08c26abe01586a82de536fa"><code>53317ad</code></a> docs: rewrite the guides around publishing, installing, and verifying (<a href="https://redirect.github.com/jdx/packslip/issues/280">#280</a>)</li> <li><a href="https://github.com/jdx/packslip/commit/126fd4c40e4f6b3909f663085e98c3d8806006db"><code>126fd4c</code></a> docs: add a generated GitHub Actions reference and keep old section links wor...</li> <li><a href="https://github.com/jdx/packslip/commit/3905dc3f39bbfc835f79e0c74ae8243c63d20fa0"><code>3905dc3</code></a> fix(install): hold a keyless domain project to the repository that signed it ...</li> <li><a href="https://github.com/jdx/packslip/commit/6d208ed07984ce795247ac8607680d12f5ad61d8"><code>6d208ed</code></a> ci: commit the verify report schema when Renovate regenerates rendered files ...</li> <li>Additional commits viewable in <a href="https://github.com/jdx/packslip/compare/7b32cd29a9240927882ee18b3db1dcfd8e0328b4...ddcddd9c8c33977d2d08d5db91caec579da59aab">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> |
||
|
|
ea5a21f11f |
chore: bump the docs-site group across 1 directory with 5 updates (#4589)
Bumps the docs-site group with 5 updates in the /docs directory: | Package | From | To | | --- | --- | --- | | [@astrojs/markdown-remark](https://github.com/withastro/astro/tree/HEAD/packages/markdown/remark) | `7.3.2` | `7.3.4` | | [@expressive-code/core](https://github.com/expressive-code/expressive-code/tree/HEAD/packages/@expressive-code/core) | `0.44.2` | `0.44.3` | | [astro](https://github.com/withastro/astro/tree/HEAD/packages/astro) | `7.3.8` | `7.4.2` | | [@astrojs/check](https://github.com/withastro/astro/tree/HEAD/packages/language-tools/astro-check) | `0.9.10` | `0.9.12` | | [playwright](https://github.com/microsoft/playwright) | `1.64.0` | `1.64.1` | Updates `@astrojs/markdown-remark` from 7.3.2 to 7.3.4 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/withastro/astro/releases">@astrojs/markdown-remark's releases</a>.</em></p> <blockquote> <h2><code>@astrojs/markdown-remark</code><a href="https://github.com/7"><code>@7</code></a>.3.4</h2> <h3>Patch Changes</h3> <ul> <li>Updated dependencies [<a href="https://github.com/withastro/astro/commit/cf27e70a9057ce29ade2a8a843bd9275a696e9ab"><code>cf27e70</code></a>]: <ul> <li><code>@astrojs/prism</code><a href="https://github.com/4"><code>@4</code></a>.1.1</li> </ul> </li> </ul> <h2><code>@astrojs/markdown-remark</code><a href="https://github.com/7"><code>@7</code></a>.3.3</h2> <h3>Patch Changes</h3> <ul> <li><a href="https://redirect.github.com/withastro/astro/pull/17894">#17894</a> <a href="https://github.com/withastro/astro/commit/b7a1bd99ac7c68cf36078058f15f1bd1fab4cbe8"><code>b7a1bd9</code></a> Thanks <a href="https://github.com/Princesseuh"><code>@Princesseuh</code></a>! - Adds the measurements that <code>astro build --timings</code> reports for Markdown processing and syntax highlighting.</li> <li>Updated dependencies [<a href="https://github.com/withastro/astro/commit/b7a1bd99ac7c68cf36078058f15f1bd1fab4cbe8"><code>b7a1bd9</code></a>, <a href="https://github.com/withastro/astro/commit/2715958666b0a706b069d0592da3a070b3796a9b"><code>2715958</code></a>]: <ul> <li><code>@astrojs/internal-helpers</code><a href="https://github.com/0"><code>@0</code></a>.13.0</li> <li><code>@astrojs/prism</code><a href="https://github.com/4"><code>@4</code></a>.1.0</li> </ul> </li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/withastro/astro/blob/main/packages/markdown/remark/CHANGELOG.md">@astrojs/markdown-remark's changelog</a>.</em></p> <blockquote> <h2>7.3.4</h2> <h3>Patch Changes</h3> <ul> <li>Updated dependencies [<a href="https://github.com/withastro/astro/commit/cf27e70a9057ce29ade2a8a843bd9275a696e9ab"><code>cf27e70</code></a>]: <ul> <li><code>@astrojs/prism</code><a href="https://github.com/4"><code>@4</code></a>.1.1</li> </ul> </li> </ul> <h2>7.3.3</h2> <h3>Patch Changes</h3> <ul> <li><a href="https://redirect.github.com/withastro/astro/pull/17894">#17894</a> <a href="https://github.com/withastro/astro/commit/b7a1bd99ac7c68cf36078058f15f1bd1fab4cbe8"><code>b7a1bd9</code></a> Thanks <a href="https://github.com/Princesseuh"><code>@Princesseuh</code></a>! - Adds the measurements that <code>astro build --timings</code> reports for Markdown processing and syntax highlighting.</li> <li>Updated dependencies [<a href="https://github.com/withastro/astro/commit/b7a1bd99ac7c68cf36078058f15f1bd1fab4cbe8"><code>b7a1bd9</code></a>, <a href="https://github.com/withastro/astro/commit/2715958666b0a706b069d0592da3a070b3796a9b"><code>2715958</code></a>]: <ul> <li><code>@astrojs/internal-helpers</code><a href="https://github.com/0"><code>@0</code></a>.13.0</li> <li><code>@astrojs/prism</code><a href="https://github.com/4"><code>@4</code></a>.1.0</li> </ul> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/withastro/astro/commit/34c953555749223022e6bb2f02019d3515749a24"><code>34c9535</code></a> [ci] release (<a href="https://github.com/withastro/astro/tree/HEAD/packages/markdown/remark/issues/18459">#18459</a>)</li> <li><a href="https://github.com/withastro/astro/commit/c2c43a99f4d50676456c137ff88359579f78bf5c"><code>c2c43a9</code></a> [ci] release (<a href="https://github.com/withastro/astro/tree/HEAD/packages/markdown/remark/issues/18354">#18354</a>)</li> <li><a href="https://github.com/withastro/astro/commit/73b3c26d5b0f3739cf1a68defb692e25efeb7724"><code>73b3c26</code></a> Update dependency rolldown to ^1.2.13 (<a href="https://github.com/withastro/astro/tree/HEAD/packages/markdown/remark/issues/18384">#18384</a>)</li> <li><a href="https://github.com/withastro/astro/commit/b7a1bd99ac7c68cf36078058f15f1bd1fab4cbe8"><code>b7a1bd9</code></a> feat(build): add a --timings flag to astro build (<a href="https://github.com/withastro/astro/tree/HEAD/packages/markdown/remark/issues/17894">#17894</a>)</li> <li><a href="https://github.com/withastro/astro/commit/eee0d1923f2bbaf70210bc1b5451ccfbfd698f4e"><code>eee0d19</code></a> Update markdown (<a href="https://github.com/withastro/astro/tree/HEAD/packages/markdown/remark/issues/18302">#18302</a>)</li> <li><a href="https://github.com/withastro/astro/commit/882dd98cd9f11c4e7bd0b812d37f865dfca75d3d"><code>882dd98</code></a> Replace esbuild with Vite and Rolldown APIs (<a href="https://github.com/withastro/astro/tree/HEAD/packages/markdown/remark/issues/18263">#18263</a>)</li> <li><a href="https://github.com/withastro/astro/commit/e5eae028ce27a5c32751f2008f4cbf70217ab61b"><code>e5eae02</code></a> Update markdown (<a href="https://github.com/withastro/astro/tree/HEAD/packages/markdown/remark/issues/18280">#18280</a>)</li> <li>See full diff in <a href="https://github.com/withastro/astro/commits/@astrojs/markdown-remark@7.3.4/packages/markdown/remark">compare view</a></li> </ul> </details> <br /> Updates `@expressive-code/core` from 0.44.2 to 0.44.3 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/expressive-code/expressive-code/releases">@expressive-code/core's releases</a>.</em></p> <blockquote> <h2><code>@expressive-code/core</code><a href="https://github.com/0"><code>@0</code></a>.44.3</h2> <h3>Patch Changes</h3> <ul> <li>4612143: Updates <code>postcss-nested</code> dependency</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/expressive-code/expressive-code/blob/main/packages/@expressive-code/core/CHANGELOG.md">@expressive-code/core's changelog</a>.</em></p> <blockquote> <h2>0.44.3</h2> <h3>Patch Changes</h3> <ul> <li>4612143: Updates <code>postcss-nested</code> dependency</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/expressive-code/expressive-code/commit/5e795d7495348c041c474a6f60a7cbb63ee51adb"><code>5e795d7</code></a> [CI] Release (<a href="https://github.com/expressive-code/expressive-code/tree/HEAD/packages/@expressive-code/core/issues/479">#479</a>)</li> <li><a href="https://github.com/expressive-code/expressive-code/commit/461214358f7d460493cacda48a5b3e1785722384"><code>4612143</code></a> Update postcss-nested to v7 (<a href="https://github.com/expressive-code/expressive-code/tree/HEAD/packages/@expressive-code/core/issues/478">#478</a>)</li> <li><a href="https://github.com/expressive-code/expressive-code/commit/f6e453886e84b31fe9033eb7a84823ba8fb96f61"><code>f6e4538</code></a> Use metaOptions instead of meta in docs plugin examples (<a href="https://github.com/expressive-code/expressive-code/tree/HEAD/packages/@expressive-code/core/issues/474">#474</a>)</li> <li>See full diff in <a href="https://github.com/expressive-code/expressive-code/commits/@expressive-code/core@0.44.3/packages/@expressive-code/core">compare view</a></li> </ul> </details> <br /> Updates `astro` from 7.3.8 to 7.4.2 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/withastro/astro/releases">astro's releases</a>.</em></p> <blockquote> <h2>astro@7.4.2</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18430">#18430</a> <a href="https://github.com/withastro/astro/commit/dda9ec395c89a1420abb3b8f88b5c7f1f385f82e"><code>dda9ec3</code></a> Thanks <a href="https://github.com/Abhirup-99"><code>@Abhirup-99</code></a>! - Speeds up content sync with <code>experimental.collectionStorage: "chunked"</code> by computing each character's UTF-8 width from its code point instead of encoding every character through <code>TextEncoder</code>. On a store of ~44k entries this cuts the chunking step from about 60 seconds to well under a second, with byte-identical output.</p> </li> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18438">#18438</a> <a href="https://github.com/withastro/astro/commit/5e0eaa4415a9081efdaeb3d9af3717ce3226ad18"><code>5e0eaa4</code></a> Thanks <a href="https://github.com/apps/astro-factory"><code>@astro-factory</code></a>! - Fixes <code>astro dev</code> with <code>@astrojs/cloudflare</code> failing with <code>Calling `require` for "node-fetch"</code> when a server dependency such as <code>cross-fetch</code> requires <code>node-fetch</code></p> </li> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18376">#18376</a> <a href="https://github.com/withastro/astro/commit/a4e201d79f19caa6bf4222f42167aeb602c066e6"><code>a4e201d</code></a> Thanks <a href="https://github.com/okxint"><code>@okxint</code></a>! - Fixes <code>astro dev</code> treating a stale lock file containing a Linux thread ID as a running Astro server. A successful process lookup with no matching PID now marks the lock as stale, preventing <code>astro dev stop</code> and <code>astro dev --force</code> from killing the unrelated process that owns the thread.</p> </li> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18467">#18467</a> <a href="https://github.com/withastro/astro/commit/d1fb7d36dad440c57d62b071e752ae220cca2baa"><code>d1fb7d3</code></a> Thanks <a href="https://github.com/apps/astro-factory"><code>@astro-factory</code></a>! - Fixes the <code>defineConfig()</code> types for <code>i18n.defaultLocale</code>, <code>i18n.fallback</code>, and <code>i18n.domains</code> so they accept a custom locale's <code>path</code> instead of its <code>codes</code>, matching how Astro validates and uses these values</p> </li> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18475">#18475</a> <a href="https://github.com/withastro/astro/commit/cf27e70a9057ce29ade2a8a843bd9275a696e9ab"><code>cf27e70</code></a> Thanks <a href="https://github.com/ematipico"><code>@ematipico</code></a>! - Bumps the minimum supported Node.js version to 22.23.4, which includes the fixes from the <a href="https://nodejs.org/en/blog/vulnerability/october-2026-security-releases">October 2026 Node.js security releases</a></p> <p>This is a patch release because the <a href="https://docs.astro.build/en/upgrade-astro/#nodejs-support-and-upgrade-policies">Node.js support and upgrade policy</a> allows the Core team to raise the minimum Maintenance LTS version in a patch release when a disclosed and fixed Node.js security flaw affects Astro.</p> </li> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18451">#18451</a> <a href="https://github.com/withastro/astro/commit/7a0ba6f48ebae256a1ce49de4f1c62c009ff94e2"><code>7a0ba6f</code></a> Thanks <a href="https://github.com/DenisCDev"><code>@DenisCDev</code></a>! - Fixes <code>astro sync</code>, <code>astro check</code> and <code>astro build</code> replacing the optimized dependencies of a dev server running in the same project, which broke framework islands in that dev server until it was restarted with <code>--force</code></p> </li> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18336">#18336</a> <a href="https://github.com/withastro/astro/commit/e943003259c3bb4d528d3d49c8ccd3eb8f84b8b5"><code>e943003</code></a> Thanks <a href="https://github.com/apps/astro-factory"><code>@astro-factory</code></a>! - Fixes inline styles in dev so that framework-transformed CSS is used, such as scoped styles and <code>v-bind()</code> in Vue single-file components</p> </li> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18399">#18399</a> <a href="https://github.com/withastro/astro/commit/829fc00629ef715fc606b89c6e684ca93f9253b9"><code>829fc00</code></a> Thanks <a href="https://github.com/apps/astro-factory"><code>@astro-factory</code></a>! - Fixes a dev server error (<code>Could not find server component name</code>) for a <code>server:defer</code> island that imports <code>astro:actions</code> or <code>astro:config/server</code>, when its page was not the first island page loaded after starting the server</p> </li> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18330">#18330</a> <a href="https://github.com/withastro/astro/commit/4db9e0d1e6a54c2300b96a0ff0cfaf5c188cecda"><code>4db9e0d</code></a> Thanks <a href="https://github.com/Samuteg"><code>@Samuteg</code></a>! - Fixes the <code>astro:env/server</code> virtual module being generated with invalid JS in dev when any environment variable contains <code>$</code> replacement patterns (<code>$`</code>, <code>$&</code>, <code>$'</code>, <code>$1</code>, …). The inlined env JSON was passed as a string to <code>String.replace</code>, so e.g. the <code>KITTY_PUBLIC_KEY</code> value set by default in Kitty terminals corrupted the module and broke dev with <code>Failed to parse source for import analysis</code></p> </li> <li> <p>Updated dependencies [<a href="https://github.com/withastro/astro/commit/cf27e70a9057ce29ade2a8a843bd9275a696e9ab"><code>cf27e70</code></a>]:</p> <ul> <li><code>@astrojs/telemetry</code><a href="https://github.com/3"><code>@3</code></a>.4.1</li> <li><code>@astrojs/markdown-satteri</code><a href="https://github.com/0"><code>@0</code></a>.4.5</li> </ul> </li> </ul> <h2>astro@7.4.1</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18425">#18425</a> <a href="https://github.com/withastro/astro/commit/6fdc36ed97316d932d2e143b85739f0af37ab329"><code>6fdc36e</code></a> Thanks <a href="https://github.com/apps/astro-factory"><code>@astro-factory</code></a>! - Preserves the last modified date of cached optimized images and incrementally restored build output when copying them into the build output on all platforms</p> </li> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18419">#18419</a> <a href="https://github.com/withastro/astro/commit/395d19525986a276bf81af7bd365e7a35dc20ef3"><code>395d195</code></a> Thanks <a href="https://github.com/apps/astro-factory"><code>@astro-factory</code></a>! - Fixes a typo in the error message shown when a font <code>cssVariable</code> is invalid</p> </li> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18401">#18401</a> <a href="https://github.com/withastro/astro/commit/484822fbba652745c4f2da5ef434a350203578e2"><code>484822f</code></a> Thanks <a href="https://github.com/danielmlr"><code>@danielmlr</code></a>! - Fixes a bug where projects whose path contains an apostrophe (<code>'</code>) failed to load sessions, middleware, a cache provider, or a <code>src/fetch.ts</code> handler</p> </li> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18407">#18407</a> <a href="https://github.com/withastro/astro/commit/a6e00beae6c134d0c1b5248eb02fbf119b7d64e9"><code>a6e00be</code></a> Thanks <a href="https://github.com/apps/astro-factory"><code>@astro-factory</code></a>! - Fixes a <code>TSCONFIG_ERROR</code> during <code>astro build</code> when a parent directory contains a <code>tsconfig.json</code> that cannot be resolved, such as one extending <code>astro/tsconfigs/strict</code> without installed dependencies</p> </li> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18427">#18427</a> <a href="https://github.com/withastro/astro/commit/908f1672a9fe6c40e6b73bfb0307f0d1f3ac2057"><code>908f167</code></a> Thanks <a href="https://github.com/apps/astro-factory"><code>@astro-factory</code></a>! - Fixes an <code>Unterminated string</code> build error when application code imports from <code>astro/config</code> (for example, <code>fontProviders</code> in a shared fonts module)</p> </li> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18428">#18428</a> <a href="https://github.com/withastro/astro/commit/40e7d54c7f969b402f011d32ccd87123835d0aa1"><code>40e7d54</code></a> Thanks <a href="https://github.com/apps/astro-factory"><code>@astro-factory</code></a>! - Fixes missing styles in production builds for conditionally rendered framework components (e.g. Svelte components inside <code>{#if}</code> blocks) imported by a hydrated island</p> </li> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18424">#18424</a> <a href="https://github.com/withastro/astro/commit/617ff59820b4a5777eb5d3765c09d29082b11acc"><code>617ff59</code></a> Thanks <a href="https://github.com/apps/astro-factory"><code>@astro-factory</code></a>! - Fixes style-only HMR in <code>.astro</code> components falling back to a full page reload when a PostCSS plugin (such as <code>@unocss/postcss</code>) lists the component as a dependency of its own style</p> </li> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18274">#18274</a> <a href="https://github.com/withastro/astro/commit/70834bbea43695c563358ea055d32ecb5e0a78dd"><code>70834bb</code></a> Thanks <a href="https://github.com/Princesseuh"><code>@Princesseuh</code></a>! - Fixes increasing memory usage when editing the Astro configuration while the dev server is running</p> </li> </ul> <h2>astro@7.4.0</h2> <h3>Minor Changes</h3> <ul> <li><a href="https://redirect.github.com/withastro/astro/pull/17894">#17894</a> <a href="https://github.com/withastro/astro/commit/b7a1bd99ac7c68cf36078058f15f1bd1fab4cbe8"><code>b7a1bd9</code></a> Thanks <a href="https://github.com/Princesseuh"><code>@Princesseuh</code></a>! - Adds a new <code>--timings</code> flag to <code>astro build</code> to help you find what slows down your builds</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/withastro/astro/blob/main/packages/astro/CHANGELOG.md">astro's changelog</a>.</em></p> <blockquote> <h2>7.4.2</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18430">#18430</a> <a href="https://github.com/withastro/astro/commit/dda9ec395c89a1420abb3b8f88b5c7f1f385f82e"><code>dda9ec3</code></a> Thanks <a href="https://github.com/Abhirup-99"><code>@Abhirup-99</code></a>! - Speeds up content sync with <code>experimental.collectionStorage: "chunked"</code> by computing each character's UTF-8 width from its code point instead of encoding every character through <code>TextEncoder</code>. On a store of ~44k entries this cuts the chunking step from about 60 seconds to well under a second, with byte-identical output.</p> </li> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18438">#18438</a> <a href="https://github.com/withastro/astro/commit/5e0eaa4415a9081efdaeb3d9af3717ce3226ad18"><code>5e0eaa4</code></a> Thanks <a href="https://github.com/apps/astro-factory"><code>@astro-factory</code></a>! - Fixes <code>astro dev</code> with <code>@astrojs/cloudflare</code> failing with <code>Calling `require` for "node-fetch"</code> when a server dependency such as <code>cross-fetch</code> requires <code>node-fetch</code></p> </li> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18376">#18376</a> <a href="https://github.com/withastro/astro/commit/a4e201d79f19caa6bf4222f42167aeb602c066e6"><code>a4e201d</code></a> Thanks <a href="https://github.com/okxint"><code>@okxint</code></a>! - Fixes <code>astro dev</code> treating a stale lock file containing a Linux thread ID as a running Astro server. A successful process lookup with no matching PID now marks the lock as stale, preventing <code>astro dev stop</code> and <code>astro dev --force</code> from killing the unrelated process that owns the thread.</p> </li> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18467">#18467</a> <a href="https://github.com/withastro/astro/commit/d1fb7d36dad440c57d62b071e752ae220cca2baa"><code>d1fb7d3</code></a> Thanks <a href="https://github.com/apps/astro-factory"><code>@astro-factory</code></a>! - Fixes the <code>defineConfig()</code> types for <code>i18n.defaultLocale</code>, <code>i18n.fallback</code>, and <code>i18n.domains</code> so they accept a custom locale's <code>path</code> instead of its <code>codes</code>, matching how Astro validates and uses these values</p> </li> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18475">#18475</a> <a href="https://github.com/withastro/astro/commit/cf27e70a9057ce29ade2a8a843bd9275a696e9ab"><code>cf27e70</code></a> Thanks <a href="https://github.com/ematipico"><code>@ematipico</code></a>! - Bumps the minimum supported Node.js version to 22.23.4, which includes the fixes from the <a href="https://nodejs.org/en/blog/vulnerability/october-2026-security-releases">October 2026 Node.js security releases</a></p> <p>This is a patch release because the <a href="https://docs.astro.build/en/upgrade-astro/#nodejs-support-and-upgrade-policies">Node.js support and upgrade policy</a> allows the Core team to raise the minimum Maintenance LTS version in a patch release when a disclosed and fixed Node.js security flaw affects Astro.</p> </li> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18451">#18451</a> <a href="https://github.com/withastro/astro/commit/7a0ba6f48ebae256a1ce49de4f1c62c009ff94e2"><code>7a0ba6f</code></a> Thanks <a href="https://github.com/DenisCDev"><code>@DenisCDev</code></a>! - Fixes <code>astro sync</code>, <code>astro check</code> and <code>astro build</code> replacing the optimized dependencies of a dev server running in the same project, which broke framework islands in that dev server until it was restarted with <code>--force</code></p> </li> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18336">#18336</a> <a href="https://github.com/withastro/astro/commit/e943003259c3bb4d528d3d49c8ccd3eb8f84b8b5"><code>e943003</code></a> Thanks <a href="https://github.com/apps/astro-factory"><code>@astro-factory</code></a>! - Fixes inline styles in dev so that framework-transformed CSS is used, such as scoped styles and <code>v-bind()</code> in Vue single-file components</p> </li> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18399">#18399</a> <a href="https://github.com/withastro/astro/commit/829fc00629ef715fc606b89c6e684ca93f9253b9"><code>829fc00</code></a> Thanks <a href="https://github.com/apps/astro-factory"><code>@astro-factory</code></a>! - Fixes a dev server error (<code>Could not find server component name</code>) for a <code>server:defer</code> island that imports <code>astro:actions</code> or <code>astro:config/server</code>, when its page was not the first island page loaded after starting the server</p> </li> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18330">#18330</a> <a href="https://github.com/withastro/astro/commit/4db9e0d1e6a54c2300b96a0ff0cfaf5c188cecda"><code>4db9e0d</code></a> Thanks <a href="https://github.com/Samuteg"><code>@Samuteg</code></a>! - Fixes the <code>astro:env/server</code> virtual module being generated with invalid JS in dev when any environment variable contains <code>$</code> replacement patterns (<code>$`</code>, <code>$&</code>, <code>$'</code>, <code>$1</code>, …). The inlined env JSON was passed as a string to <code>String.replace</code>, so e.g. the <code>KITTY_PUBLIC_KEY</code> value set by default in Kitty terminals corrupted the module and broke dev with <code>Failed to parse source for import analysis</code></p> </li> <li> <p>Updated dependencies [<a href="https://github.com/withastro/astro/commit/cf27e70a9057ce29ade2a8a843bd9275a696e9ab"><code>cf27e70</code></a>]:</p> <ul> <li><code>@astrojs/telemetry</code><a href="https://github.com/3"><code>@3</code></a>.4.1</li> <li><code>@astrojs/markdown-satteri</code><a href="https://github.com/0"><code>@0</code></a>.4.5</li> </ul> </li> </ul> <h2>7.4.1</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18425">#18425</a> <a href="https://github.com/withastro/astro/commit/6fdc36ed97316d932d2e143b85739f0af37ab329"><code>6fdc36e</code></a> Thanks <a href="https://github.com/apps/astro-factory"><code>@astro-factory</code></a>! - Preserves the last modified date of cached optimized images and incrementally restored build output when copying them into the build output on all platforms</p> </li> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18419">#18419</a> <a href="https://github.com/withastro/astro/commit/395d19525986a276bf81af7bd365e7a35dc20ef3"><code>395d195</code></a> Thanks <a href="https://github.com/apps/astro-factory"><code>@astro-factory</code></a>! - Fixes a typo in the error message shown when a font <code>cssVariable</code> is invalid</p> </li> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18401">#18401</a> <a href="https://github.com/withastro/astro/commit/484822fbba652745c4f2da5ef434a350203578e2"><code>484822f</code></a> Thanks <a href="https://github.com/danielmlr"><code>@danielmlr</code></a>! - Fixes a bug where projects whose path contains an apostrophe (<code>'</code>) failed to load sessions, middleware, a cache provider, or a <code>src/fetch.ts</code> handler</p> </li> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18407">#18407</a> <a href="https://github.com/withastro/astro/commit/a6e00beae6c134d0c1b5248eb02fbf119b7d64e9"><code>a6e00be</code></a> Thanks <a href="https://github.com/apps/astro-factory"><code>@astro-factory</code></a>! - Fixes a <code>TSCONFIG_ERROR</code> during <code>astro build</code> when a parent directory contains a <code>tsconfig.json</code> that cannot be resolved, such as one extending <code>astro/tsconfigs/strict</code> without installed dependencies</p> </li> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18427">#18427</a> <a href="https://github.com/withastro/astro/commit/908f1672a9fe6c40e6b73bfb0307f0d1f3ac2057"><code>908f167</code></a> Thanks <a href="https://github.com/apps/astro-factory"><code>@astro-factory</code></a>! - Fixes an <code>Unterminated string</code> build error when application code imports from <code>astro/config</code> (for example, <code>fontProviders</code> in a shared fonts module)</p> </li> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18428">#18428</a> <a href="https://github.com/withastro/astro/commit/40e7d54c7f969b402f011d32ccd87123835d0aa1"><code>40e7d54</code></a> Thanks <a href="https://github.com/apps/astro-factory"><code>@astro-factory</code></a>! - Fixes missing styles in production builds for conditionally rendered framework components (e.g. Svelte components inside <code>{#if}</code> blocks) imported by a hydrated island</p> </li> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18424">#18424</a> <a href="https://github.com/withastro/astro/commit/617ff59820b4a5777eb5d3765c09d29082b11acc"><code>617ff59</code></a> Thanks <a href="https://github.com/apps/astro-factory"><code>@astro-factory</code></a>! - Fixes style-only HMR in <code>.astro</code> components falling back to a full page reload when a PostCSS plugin (such as <code>@unocss/postcss</code>) lists the component as a dependency of its own style</p> </li> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18274">#18274</a> <a href="https://github.com/withastro/astro/commit/70834bbea43695c563358ea055d32ecb5e0a78dd"><code>70834bb</code></a> Thanks <a href="https://github.com/Princesseuh"><code>@Princesseuh</code></a>! - Fixes increasing memory usage when editing the Astro configuration while the dev server is running</p> </li> </ul> <h2>7.4.0</h2> <h3>Minor Changes</h3> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/withastro/astro/commit/34c953555749223022e6bb2f02019d3515749a24"><code>34c9535</code></a> [ci] release (<a href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/18459">#18459</a>)</li> <li><a href="https://github.com/withastro/astro/commit/cf27e70a9057ce29ade2a8a843bd9275a696e9ab"><code>cf27e70</code></a> fix: minimal support node version (<a href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/18475">#18475</a>)</li> <li><a href="https://github.com/withastro/astro/commit/1efb9d60e59ba7081f28e1f99d557468a5ea48eb"><code>1efb9d6</code></a> Update dependency <code>@playwright/test</code> to v1.64.1 (<a href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/18441">#18441</a>)</li> <li><a href="https://github.com/withastro/astro/commit/5e0eaa4415a9081efdaeb3d9af3717ce3226ad18"><code>5e0eaa4</code></a> fix(astro): stop excluding node-fetch from server dep optimization in workerd...</li> <li><a href="https://github.com/withastro/astro/commit/a4e201d79f19caa6bf4222f42167aeb602c066e6"><code>a4e201d</code></a> fix(dev): treat missing ps row as stale in lockfile process check (<a href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/18376">#18376</a>)</li> <li><a href="https://github.com/withastro/astro/commit/7a0ba6f48ebae256a1ce49de4f1c62c009ff94e2"><code>7a0ba6f</code></a> Use a separate Vite cache for the temporary sync server (<a href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/18451">#18451</a>)</li> <li><a href="https://github.com/withastro/astro/commit/d1fb7d36dad440c57d62b071e752ae220cca2baa"><code>d1fb7d3</code></a> fix(i18n): use locale path instead of codes in defineConfig i18n types (<a href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/18467">#18467</a>)</li> <li><a href="https://github.com/withastro/astro/commit/dda9ec395c89a1420abb3b8f88b5c7f1f385f82e"><code>dda9ec3</code></a> fix(content): compute UTF-8 width arithmetically in getChunkEnd (<a href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/18430">#18430</a>)</li> <li><a href="https://github.com/withastro/astro/commit/7af66fc785d85b1df1f98e7123a52b2306250985"><code>7af66fc</code></a> Fix astro-check binary silently dropping the first two CLI arguments (<a href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/18455">#18455</a>)</li> <li><a href="https://github.com/withastro/astro/commit/829fc00629ef715fc606b89c6e684ca93f9253b9"><code>829fc00</code></a> Skip server island manifest in CSS ensureModulesLoaded to fix late-discovery ...</li> <li>Additional commits viewable in <a href="https://github.com/withastro/astro/commits/astro@7.4.2/packages/astro">compare view</a></li> </ul> </details> <br /> Updates `@astrojs/check` from 0.9.10 to 0.9.12 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/withastro/astro/releases">@astrojs/check's releases</a>.</em></p> <blockquote> <h2><code>@astrojs/check</code><a href="https://github.com/0"><code>@0</code></a>.9.12</h2> <h3>Patch Changes</h3> <ul> <li><a href="https://redirect.github.com/withastro/astro/pull/18455">#18455</a> <a href="https://github.com/withastro/astro/commit/7af66fc785d85b1df1f98e7123a52b2306250985"><code>7af66fc</code></a> Thanks <a href="https://github.com/apps/astro-factory"><code>@astro-factory</code></a>! - Fixes the <code>astro-check</code> binary ignoring its first two command-line arguments, so flags such as <code>--help</code>, <code>--root</code>, <code>--watch</code>, and <code>--tsconfig</code> are respected again. If your scripts padded the arguments to work around this (for example, <code>astro-check -- -- --tsconfig ./tsconfig.app.json</code>), remove the padding.</li> <li>Updated dependencies [<a href="https://github.com/withastro/astro/commit/044148d5cfbc90e0277b3205a52ec73bc452bb7e"><code>044148d</code></a>]: <ul> <li><code>@astrojs/language-server</code><a href="https://github.com/2"><code>@2</code></a>.17.3</li> </ul> </li> </ul> <h2><code>@astrojs/check</code><a href="https://github.com/0"><code>@0</code></a>.9.11</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18445">#18445</a> <a href="https://github.com/withastro/astro/commit/d736df7a9cc03c12b22e538f058fb1f769672471"><code>d736df7</code></a> Thanks <a href="https://github.com/apps/astro-factory"><code>@astro-factory</code></a>! - Fixes the <code>--preserveWatchOutput</code> help text, which described the opposite of the flag's behavior. Setting it to <code>true</code> keeps output between checks in watch mode.</p> </li> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18444">#18444</a> <a href="https://github.com/withastro/astro/commit/c55134c1d3c238a43e17cfeff136375a4d9d5d35"><code>c55134c</code></a> Thanks <a href="https://github.com/apps/astro-factory"><code>@astro-factory</code></a>! - Fixes <code>astro check --watch</code> exiting immediately when the project path contains <code>node_modules</code> or <code>.git</code></p> </li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/withastro/astro/blob/main/packages/language-tools/astro-check/CHANGELOG.md">@astrojs/check's changelog</a>.</em></p> <blockquote> <h2>0.9.12</h2> <h3>Patch Changes</h3> <ul> <li><a href="https://redirect.github.com/withastro/astro/pull/18455">#18455</a> <a href="https://github.com/withastro/astro/commit/7af66fc785d85b1df1f98e7123a52b2306250985"><code>7af66fc</code></a> Thanks <a href="https://github.com/apps/astro-factory"><code>@astro-factory</code></a>! - Fixes the <code>astro-check</code> binary ignoring its first two command-line arguments, so flags such as <code>--help</code>, <code>--root</code>, <code>--watch</code>, and <code>--tsconfig</code> are respected again. If your scripts padded the arguments to work around this (for example, <code>astro-check -- -- --tsconfig ./tsconfig.app.json</code>), remove the padding.</li> <li>Updated dependencies [<a href="https://github.com/withastro/astro/commit/044148d5cfbc90e0277b3205a52ec73bc452bb7e"><code>044148d</code></a>]: <ul> <li><code>@astrojs/language-server</code><a href="https://github.com/2"><code>@2</code></a>.17.3</li> </ul> </li> </ul> <h2>0.9.11</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18445">#18445</a> <a href="https://github.com/withastro/astro/commit/d736df7a9cc03c12b22e538f058fb1f769672471"><code>d736df7</code></a> Thanks <a href="https://github.com/apps/astro-factory"><code>@astro-factory</code></a>! - Fixes the <code>--preserveWatchOutput</code> help text, which described the opposite of the flag's behavior. Setting it to <code>true</code> keeps output between checks in watch mode.</p> </li> <li> <p><a href="https://redirect.github.com/withastro/astro/pull/18444">#18444</a> <a href="https://github.com/withastro/astro/commit/c55134c1d3c238a43e17cfeff136375a4d9d5d35"><code>c55134c</code></a> Thanks <a href="https://github.com/apps/astro-factory"><code>@astro-factory</code></a>! - Fixes <code>astro check --watch</code> exiting immediately when the project path contains <code>node_modules</code> or <code>.git</code></p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/withastro/astro/commit/34c953555749223022e6bb2f02019d3515749a24"><code>34c9535</code></a> [ci] release (<a href="https://github.com/withastro/astro/tree/HEAD/packages/language-tools/astro-check/issues/18459">#18459</a>)</li> <li><a href="https://github.com/withastro/astro/commit/7af66fc785d85b1df1f98e7123a52b2306250985"><code>7af66fc</code></a> Fix astro-check binary silently dropping the first two CLI arguments (<a href="https://github.com/withastro/astro/tree/HEAD/packages/language-tools/astro-check/issues/18455">#18455</a>)</li> <li><a href="https://github.com/withastro/astro/commit/e990df87fb74b71a94b50fbc83a26a189391e300"><code>e990df8</code></a> [ci] release (<a href="https://github.com/withastro/astro/tree/HEAD/packages/language-tools/astro-check/issues/18405">#18405</a>)</li> <li><a href="https://github.com/withastro/astro/commit/c55134c1d3c238a43e17cfeff136375a4d9d5d35"><code>c55134c</code></a> Fix <code>astro check --watch</code> exiting immediately when project path contains `nod...</li> <li><a href="https://github.com/withastro/astro/commit/d736df7a9cc03c12b22e538f058fb1f769672471"><code>d736df7</code></a> Correct --preserveWatchOutput help text in astro check (<a href="https://github.com/withastro/astro/tree/HEAD/packages/language-tools/astro-check/issues/18445">#18445</a>)</li> <li><a href="https://github.com/withastro/astro/commit/21feaab7ae808a0e6001865c71c3de3096fe13f2"><code>21feaab</code></a> Update language-tools (<a href="https://github.com/withastro/astro/tree/HEAD/packages/language-tools/astro-check/issues/18347">#18347</a>)</li> <li><a href="https://github.com/withastro/astro/commit/421d4a670dfe109d491a2b82768c1dbc2d6f7403"><code>421d4a6</code></a> Update dependency <code>@astrojs/language-server</code> to ^2.17.1 (<a href="https://github.com/withastro/astro/tree/HEAD/packages/language-tools/astro-check/issues/18320">#18320</a>)</li> <li><a href="https://github.com/withastro/astro/commit/134af3e6d4a670046e56226b03436d6a1c8a2fa6"><code>134af3e</code></a> Update language-tools (<a href="https://github.com/withastro/astro/tree/HEAD/packages/language-tools/astro-check/issues/18312">#18312</a>)</li> <li><a href="https://github.com/withastro/astro/commit/da1333a4f6754ee6311e06532030829f2544dde6"><code>da1333a</code></a> Update dependency chokidar to v5 (<a href="https://github.com/withastro/astro/tree/HEAD/packages/language-tools/astro-check/issues/18107">#18107</a>)</li> <li><a href="https://github.com/withastro/astro/commit/7cc0b0076e9630e3ced20e44950eee1a9ce6fb5a"><code>7cc0b00</code></a> Update language-tools (<a href="https://github.com/withastro/astro/tree/HEAD/packages/language-tools/astro-check/issues/17578">#17578</a>)</li> <li>See full diff in <a href="https://github.com/withastro/astro/commits/@astrojs/check@0.9.12/packages/language-tools/astro-check">compare view</a></li> </ul> </details> <br /> Updates `playwright` from 1.64.0 to 1.64.1 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/microsoft/playwright/releases">playwright's releases</a>.</em></p> <blockquote> <h2>v1.64.1</h2> <h3>Bug Fixes</h3> <ul> <li><a href="https://redirect.github.com/microsoft/playwright/issues/43247">#43247</a> [Bug]: _electron.launch intermittently loses a packaged app's first window since 1.64.0</li> <li><a href="https://redirect.github.com/microsoft/playwright/issues/43242">#43242</a> [Regression]: Chromium 155+ aborts a preflighted cross-origin redirect whenever any route is registered (net::ERR_ABORTED)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/microsoft/playwright/commit/cfe490d941f992655948eee8fd4fd94e1c4234bf"><code>cfe490d</code></a> cherry-pick(<a href="https://redirect.github.com/microsoft/playwright/issues/43353">#43353</a>): docs: release notes for v1.64 Python</li> <li><a href="https://github.com/microsoft/playwright/commit/866cbb864009f84d7e8e41c64fdbfceff43f280d"><code>866cbb8</code></a> chore: mark v1.64.1 (<a href="https://redirect.github.com/microsoft/playwright/issues/43354">#43354</a>)</li> <li><a href="https://github.com/microsoft/playwright/commit/1b2924712024804936dbcfe9fabaa655d52325e5"><code>1b29247</code></a> cherry-pick(<a href="https://redirect.github.com/microsoft/playwright/issues/43250">#43250</a>): fix(electron): do not drop windows that have not navigat...</li> <li><a href="https://github.com/microsoft/playwright/commit/632d976826c74b0163fd5201a05b7b4853ba3f4a"><code>632d976</code></a> cherry-pick(<a href="https://redirect.github.com/microsoft/playwright/issues/43249">#43249</a>): fix(chromium): disable AvoidCorsURLLoaderRestartOnRedirect</li> <li><a href="https://github.com/microsoft/playwright/commit/824d0c5d1e10f21fcbe88d18a99d06194acde77c"><code>824d0c5</code></a> cherry-pick(<a href="https://redirect.github.com/microsoft/playwright/issues/43217">#43217</a>): chore(dotnet): fix async suffix of optional-arg overload...</li> <li>See full diff in <a href="https://github.com/microsoft/playwright/compare/v1.64.0...v1.64.1">compare view</a></li> </ul> </details> <br /> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> |
||
|
|
f98692b7d6 |
chore: bump astral-sh/setup-uv from 10.3.0 to 10.3.2 in /.github/actions/tend-setup (#4594)
Bumps [astral-sh/setup-uv](https://github.com/astral-sh/setup-uv) from 10.3.0 to 10.3.2. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/astral-sh/setup-uv/releases">astral-sh/setup-uv's releases</a>.</em></p> <blockquote> <h2>v10.3.2 🌈 update known checksums for 0.13.5</h2> <h2>Changes</h2> <h2>🧰 Maintenance</h2> <ul> <li>chore: update known checksums for 0.13.5 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1103">#1103</a>)</li> </ul> <h2>📚 Documentation</h2> <ul> <li>docs: update version references to v10.3.1 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1102">#1102</a>)</li> </ul> <h2>v10.3.1 🌈 preserve cache error class names in save-cache bundle</h2> <h2>Changes</h2> <p>This release includes a fix so that multiple concurrent workflows trying to upload the same cache no longer warn</p> <p><code>##[warning]Failed to save: Unable to reserve cache with key ..., another job may be creating this cache.</code></p> <h2>🐛 Bug fixes</h2> <ul> <li>fix: preserve cache error class names in save-cache bundle <a href="https://github.com/dannyward630"><code>@dannyward630</code></a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1093">#1093</a>)</li> </ul> <h2>🧰 Maintenance</h2> <ul> <li>chore: update known checksums for 0.13.4 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1099">#1099</a>)</li> <li>chore: update known checksums for 0.13.2/0.13.3 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1098">#1098</a>)</li> <li>chore: update known checksums for 0.13.1 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1094">#1094</a>)</li> <li>Verify npm dependency signatures before builds <a href="https://github.com/zaniebot"><code>@zaniebot</code></a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1027">#1027</a>)</li> </ul> <h2>📚 Documentation</h2> <ul> <li>docs: cache-dependency-glob matches relative to the working directory <a href="https://github.com/flange-ipb"><code>@flange-ipb</code></a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1092">#1092</a>)</li> <li>docs: update version references to v10.3.0 @<a href="https://github.com/apps/github-actions">github-actions[bot]</a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1090">#1090</a>)</li> </ul> <h2>⬆️ Dependency updates</h2> <ul> <li>chore(deps): roll up Dependabot updates <a href="https://github.com/eifinger"><code>@eifinger</code></a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1101">#1101</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/astral-sh/setup-uv/commit/07a047e608db84b3d8c06cd9a7c7dcc9c355c18e"><code>07a047e</code></a> chore: update known checksums for 0.13.5 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1103">#1103</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/e1b85369e72750369c935b004eccf97311bdf5dc"><code>e1b8536</code></a> docs: update version references to v10.3.1 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1102">#1102</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/18d369b23da25a81e9458561248e1aafff6a70fa"><code>18d369b</code></a> chore(deps): roll up Dependabot updates (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1101">#1101</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/4ad2329c1e377d882fcae221cd1d17e7c0ad788e"><code>4ad2329</code></a> chore: update known checksums for 0.13.4 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1099">#1099</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/4bc6759c82322ff7efa28de54a45404ca6869912"><code>4bc6759</code></a> chore: update known checksums for 0.13.2/0.13.3 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1098">#1098</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/c97f06e356bcca1b426f396ef93ec35ce149ce7b"><code>c97f06e</code></a> fix: preserve cache error class names in save-cache bundle (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1093">#1093</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/8ca4be000bfa5f8e6aaa01d8470878c90aa728d3"><code>8ca4be0</code></a> chore: update known checksums for 0.13.1 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1094">#1094</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/b627d85691ead579b598a36169571b1c7123526f"><code>b627d85</code></a> docs: cache-dependency-glob matches relative to the working directory (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1092">#1092</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/f8c88970fcd8fff8e97bc62edc5f5c073a0527fe"><code>f8c8897</code></a> Verify npm dependency signatures before builds (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1027">#1027</a>)</li> <li><a href="https://github.com/astral-sh/setup-uv/commit/f64d32b1cd6cc11405a74665b3dfb7bb86fea9f0"><code>f64d32b</code></a> docs: update version references to v10.3.0 (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/1090">#1090</a>)</li> <li>See full diff in <a href="https://github.com/astral-sh/setup-uv/compare/v10.3.0...v10.3.2">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> |
||
|
|
a6c26c787e |
Retain partial JSON results when later command steps fail (#4584)
Preserve confirmed work in JSON output when a later command step fails. For example, a switch that creates a worktree before `--execute` fails still reports the created path; push and merge retain a completed target update if final verification fails. Command payloads stay on stdout, readable diagnostics stay on stderr, and the exit status signals failure. Carry typed partial facts across mutation boundaries and serialize them in the command handlers. This covers switch, commit/squash, merge/push, remove/prune, relocation, and copy-ignored without adding a public result/error envelope. Switch failures before any result exists now leave stdout empty instead of returning an error-only JSON object. Help and regression tests document the contract. Validation: 309 focused tests and nine additional boundary cases passed, including late commit/squash, prune, relocation, and detached-removal failures and skipped-copy accounting. Clippy, pre-commit, documentation checks, and doctests passed. The full local gate had 12 failures: nine passed sequentially, while three PowerShell tests reproduced `Stack overflow.`. After integrating current main, all-target/all-feature compilation and a review of the overlapping changes passed. CI remains the merge gate. > _This was written by Codex on behalf of max-sixty_ |
||
|
|
c0a2b50bc9 |
Move the full-page demo link below the workspace (#4581)
Start the Try it page directly with the workspace and place the full-page Demoshell link underneath. Reserve the link’s rendered height and spacing in the viewport sizing, including when it wraps, so it stays visible below the demo. Validated with the docs sync test, Astro check/build, pre-commit checks, and desktop/mobile preview inspection. > _This was written by Codex on behalf of max-sixty_ |
||
|
|
1ec56f3073 |
Make the Try it demo a viewport-sized workspace (#4579)
The Try it page squeezed the terminal and guide into a reading column and required scrolling between them. Use one heading and one full-page Demoshell link, align the heading with the documentation rail, and let the demo fill the main pane’s available width and remaining viewport height. Omit this page’s footer and reserve space for Demoshell’s attribution so it cannot cover the mobile checklist control. Validated with the docs sync test, Astro check/build, pre-commit checks, an independent demo walkthrough, and desktop/mobile browser checks. Demoshell blocks local preview origins, so the running VM’s layout was checked with temporary candidate styling and sizing code on the production page. The [Demoshell status-row background issue](https://github.com/max-sixty/worktrunk/pull/4280#issuecomment-6356874760) remains with the provider. > _This was written by Codex on behalf of max-sixty_ |
||
|
|
90da2475b0 |
Reclaim stale temporary indexes with age-based cleanup (#4469)
Abruptly terminated commands can leave full temporary Git index copies behind. The contributor reported 52,786 files totaling 127 GB after three days of frequent statusline cancellations. Reclaim index copies and their Git lock siblings older than one hour when a command next creates a temporary index. Keep the existing filename prefix so cleanup also handles files left by older versions. Sweep the system temp directory once per process, without making other probe threads wait, and retain best-effort cleanup in the Git-directory fallback. Normal exits still remove their own temporary indexes. This uses age alone: no PID-tagged filenames, process checks, or platform-specific liveness behavior. Move commit-preview approval before temporary-index creation so an unattended approval prompt cannot age out an index needed afterward. The one-hour limit is a retention policy; a suspended operation or unusually slow Git filter can still exceed it. Statusline computations are unchanged. Validation: regression tests cover stale indexes and locks, recent/future/unrelated files, both storage locations, cleanup failures, real-index preservation, and the actual approval wait. The approval test fails with the old ordering and passes with the fix. Independent review, lint, docs sync, and docs build passed. The local full gate passed 5,412 tests; three PowerShell tests failed because the installed pwsh also crashes with Stack overflow on a standalone arithmetic command outside the repository. > _This was written by Codex on behalf of max-sixty_ --------- Co-authored-by: Jonah Eaton <49370794+jonaheaton@users.noreply.github.com> Co-authored-by: Claude Opus 5 <noreply@anthropic.com> Co-authored-by: Maximilian Roos <m@maxroos.com> |
||
|
|
bc828a7143 |
Report unreadable config files and share layer loading (#4564)
Unreadable system and user config files are silently ignored, allowing commands such as `switch --create` to proceed with defaults. Load both file layers through one ordered loop and distinguish an absent file from a read failure. Strict commands report read failures; best-effort callers retain usable settings from other layers. Missing-file behavior and layer precedence stay the same. The shared path removes 25 lines of duplicated loading logic. Update the save-failure prompt test to make the path unwritable after the prompt appears, using the existing callback; it now isolates a save failure from a startup read failure. Depends on #4563 and targets its branch. Validation: all four new regressions reproduce branch creation with the old loader for directories and invalid UTF-8 in user/system files. All 416 focused config tests pass. The required `cargo run -- hook pre-merge --yes` gate passed in the combined audit checkout: 5,469 tests passed, one skipped, plus formatting, Clippy, lockfile checks, doctests, and rustdoc. The container runner supplied orphan reaping because its PID 1 does not reap children. --------- Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com> |
||
|
|
836ec72c4f |
Use parsed command context for hook-name completion (#4560)
Hook-name completion currently scans every raw argument for a hook type. A config filename, earlier filter, or word after the cursor named `pre-switch` can make completion suggest hooks from the wrong lifecycle stage. Carry the hook type from the existing early Clap parse into completion context and remove the duplicate raw-argument scanner. Regression coverage includes canonical hook names, aliases, misleading option values, filters, and words after the cursor. Depends on #4551; this draft targets its branch. Validation: the regression reproduces the wrong suggestions before the change, and all 129 focused completion tests pass. The required `cargo run -- hook pre-merge --yes` gate passed in the combined audit checkout: 5,469 tests passed, one skipped, plus formatting, Clippy, lockfile checks, doctests, and rustdoc. The container runner supplied orphan reaping because its PID 1 does not reap children. |
||
|
|
5c82218f28 |
Add a commit-generation command accessor and drop checked unwraps (#4558)
Add `CommitGenerationConfig::command()`, returning the configured command when it is non-empty. Generation, squash, the connectivity probe, the dry-run display, and `config show` diagnostics use it instead of `is_configured()` followed by `command.as_ref().unwrap()` or a repeated whitespace filter. No behavior change. Builds on #4553. > _This was written by Claude Code on behalf of max-sixty_ --------- Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com> |
||
|
|
d187abf90b |
Skip non-UTF-8 environment entries instead of panicking in config loading (#4563)
`std::env::vars()` panics when any environment entry is not valid UTF-8, so an unrelated variable could crash config loading. Read with `vars_os` and skip entries that don't decode; a non-UTF-8 `WORKTRUNK_*` override is ignored like any other unusable entry. > _This was written by Claude Code on behalf of max-sixty_ --------- Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com> |
||
|
|
023cb0a82d |
Propagate failed Git predicates instead of treating them as missing refs (#4562)
When a ref query fails, `wt switch --create` can treat the branch as absent and create it from a fallback base. The same predicate helper can cache a failed `merge-base --is-ancestor` (for example, a missing object) as a permanent `false`. Give `run_command_check` Git's predicate contract: status 0 is true, 1 is false, and anything else propagates the command error. `ref_exists` uses quiet `rev-parse --verify`, which follows that contract, and `exists_locally` reuses it. Switch base selection and the pre-add branch check propagate failures instead of defaulting to "absent". `wt list` now reports a failed ancestry query alongside its other failed tasks (one snapshot updated). Tests: a switch regression where a failing `rev-parse` must stop creation, and a unit test that a failed ancestry query is not cached. > _This was written by Claude Code on behalf of max-sixty_ --------- Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com> |
||
|
|
70b4082e5e |
Share LLM generation command handling across commit, squash, and diagnostics (#4553)
Commit generation, squash generation, and the `config show --full` connectivity probe each carried their own copy of the watchdog plus `LlmCommandFailed` wrapping. Route all three through one `execute_generation_command` helper; the only difference between them, the `--show-prompt` reproduction hint, is a parameter. No behavior change; existing generation and diagnostics tests cover these paths. > _This was written by Claude Code on behalf of max-sixty_ --------- Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com> |
||
|
|
6c6691b8b5 |
Use the requested repository and config for completion (#4551)
Completion exits before normal CLI parsing, so `-C`, `--config`, and `--config-set` previously had no effect on its repository/config discovery. Reuse the early global-option parser before prewarming completion caches. Only words before the cursor affect discovery, and verbose completion logs go to the selected repository. Use the selected directory for relative path candidates and custom completer processes too. Locate external commands through clap's parsed argument tail instead of assuming the command is argv[1], adjusting the forwarded cursor after global options. Editing a command name in the middle of a line no longer invokes its PATH executable. Resolve the executable before applying the child directory so relative PATH entries match runtime dispatch. Based on #4548. Reuse its alias-injected command tree while applying the parsed command offset and selected directory. Regression coverage verifies that user and project aliases in a `-C`-selected repository still take precedence over PATH executables. Validation: the required `cargo run -- hook pre-merge --yes` gate passed in the combined local audit checkout: 5,469 tests passed, one skipped, plus formatting, Clippy, lockfile checks, doctests, and rustdoc. The container runner supplied orphan reaping because its PID 1 does not reap children. |
||
|
|
ad7c68ba55 |
Complete effective hook names and source-qualified filters (#4549)
Hook-name completion reads raw global user hooks, omitting wildcard and exact per-project user settings that execution uses. Resolve the current project identity and use the same effective hook merge as execution, alongside project-file hooks. Reuse the existing hook filter parser for `user:name` and `project:name` completion. A typed source prefix now suggests qualified names from that source; unqualified completion keeps its existing behavior. Validation: the required `cargo run -- hook pre-merge --yes` gate passed in the combined local audit checkout: 5,463 tests passed, one skipped, plus formatting, Clippy, lockfile checks, doctests, and rustdoc. The container runner supplied orphan reaping because its PID 1 does not reap children. |
||
|
|
7b61087743 |
Honor alias precedence over PATH executables during completion (#4548)
When an alias and a `wt-*` executable share a name, Tab completion now follows the alias, matching runtime dispatch. Build the alias-aware command tree before deciding whether to forward completion, and reuse that tree for the single-dash fallback instead of loading configs and scanning PATH twice. Validation: the required `cargo run -- hook pre-merge --yes` gate passed in the combined local audit checkout: 5,463 tests passed, one skipped, plus formatting, Clippy, lockfile checks, doctests, and rustdoc. The container runner supplied orphan reaping because its PID 1 does not reap children. |
||
|
|
d15ba8e529 |
Reject invalid alias arguments without falling through to PATH (#4550)
Passing a non-UTF-8 argument to a configured alias previously skipped alias dispatch, either reporting an unknown command or running a same-named `wt-*` executable. Resolve the alias first, then report that its arguments require UTF-8. External commands still receive raw arguments unchanged. Move encoding validation into alias dispatch and reuse the already-resolved alias entry instead of looking it up again after parsing. Validation: the required `cargo run -- hook pre-merge --yes` gate passed in the combined local audit checkout: 5,463 tests passed, one skipped, plus formatting, Clippy, lockfile checks, doctests, and rustdoc. The container runner supplied orphan reaping because its PID 1 does not reap children. |
||
|
|
bf0894cb97 |
Make named alias inspection work outside repositories (#4547)
`wt config alias show deploy` now works outside a Git repository, matching the unnamed listing. Both forms share discovery and paging, retain user-before-project ordering and typo suggestions, and suppress unrelated migration warnings before config prewarming. Validation: the required `cargo run -- hook pre-merge --yes` gate passed in the combined local audit checkout: 5,463 tests passed, one skipped, plus formatting, Clippy, lockfile checks, doctests, and rustdoc. The container runner supplied orphan reaping because its PID 1 does not reap children. |
||
|
|
ee9d1b8238 |
Discover only executable custom subcommands (#4565)
On Unix, completion can list `wt-*` directories and broken or non-executable symlinks as commands. An earlier non-executable file also hides a valid executable with the same name later on PATH because names are deduplicated before validation. Use the existing `which` resolver, as runtime dispatch does, to validate candidates. Sort and deduplicate valid names at the end, removing the separate permission-bit check and seen-name set. Validation: all three regression tests fail before the change, covering directories, symlink targets, and a valid later PATH executable. All 132 completion tests pass. The required `cargo run -- hook pre-merge --yes` gate passed in the combined audit checkout: 5,463 tests passed, one skipped, plus formatting, Clippy, lockfile checks, doctests, and rustdoc. The container runner supplied orphan reaping because its PID 1 does not reap children. |
||
|
|
56c1b1534c |
Clear repeated Git config values completely (#4566)
`git config --unset` returns status 5 both when a key is absent and when it has multiple values. Worktrunk treats that status as absence, so clearing repeated state values can report success while leaving the values on disk and removing them only from the in-memory cache. Use `--unset-all` in the shared key-clearing helper. Status 5 then means absence, and a successful clear removes every value for the selected key. Add coverage for cached and fresh reads, repeated clears, and both named-variable and `--all` CLI paths. Validation: all three regressions fail before the fix. All 171 focused state, repository-config, and commit-generation prompt tests pass with the fix. The required `cargo run -- hook pre-merge --yes` gate passed in the combined audit checkout: 5,463 tests passed, one skipped, plus formatting, Clippy, lockfile checks, doctests, and rustdoc. The container runner supplied orphan reaping because its PID 1 does not reap children. |
||
|
|
1c6eb9da85 |
Test same-basename trash staging without depending on drain timing (#4561)
The same-basename prune regression assumes each removal creates a separate background-drain log. The removal path intentionally reuses a running drain, so the assertion depends on scheduling and can fail when both worktrees were correctly staged and removed. Move this invariant to the staging boundary: stage two registered worktrees with the same basename, verify that each keeps its registration-derived destination, and verify that both staged directories survive distinctly. Existing integration tests retain command-level prune coverage. No production removal behavior changes. Validation: the replacement test and 886 focused repository, switch, and prune tests pass. The required `cargo run -- hook pre-merge --yes` gate passed in the combined audit checkout: 5,463 tests passed, one skipped, plus formatting, Clippy, lockfile checks, doctests, and rustdoc. The container runner supplied orphan reaping because its PID 1 does not reap children. |
||
|
|
f5417ed346 |
refactor: share copy-ignored entry reporting (#4569)
`copy-ignored` builds the same human-readable entry list for dry-run and verbose output, and repeats the same JSON mapping for planned and completed copies. Share those two builders so path formatting, file/directory labels, pluralization, and JSON entry shapes have one implementation each. Keep the existing stdout/stderr routing and output unchanged. This only changes reporting in `copy_ignored.rs`; it does not overlap #4450's transfer and filtering changes. Validation: existing copy-ignored text and JSON snapshots pass unchanged as part of 448 focused tests. The combined audit branch passes `cargo run -- hook pre-merge --yes`: 5,463 tests passed, one skipped, plus formatting, Clippy, doctests, rustdoc, and static checks. |
||
|
|
1347baefce |
Declare shell value names directly on CLI arguments (#4554)
The shell argument usage labels are currently applied by traversing and mutating the command tree after construction. Declare the same cached value name on the init, install, and uninstall arguments, leaving `build_command` responsible only for the shared help template. Remove the obsolete TODO claiming that missing shell arguments do not show the available shells. This removes twenty-two lines without changing command syntax or help output. Validation: the required `cargo run -- hook pre-merge --yes` gate passed in the combined local audit checkout: 5,463 tests passed, one skipped, plus formatting, Clippy, lockfile checks, doctests, and rustdoc. The container runner supplied orphan reaping because its PID 1 does not reap children. |
||
|
|
43af4828d9 |
Simplify UTF-8 truncation and command suggestion handling (#4552)
Replace the two manual UTF-8 boundary loops used for completion previews and LLM line truncation with `str::floor_char_boundary`. Remove a redundant scan in command suggestion handling: the existing per-argument condition already detects options. This preserves behavior while removing ten lines. Existing truncation and suggestion tests cover these paths. Validation: the required `cargo run -- hook pre-merge --yes` gate passed in the combined local audit checkout: 5,463 tests passed, one skipped, plus formatting, Clippy, lockfile checks, doctests, and rustdoc. The container runner supplied orphan reaping because its PID 1 does not reap children. |
||
|
|
423960b2af |
docs: simplify logging and integration guidance (#4576)
Trim repeated explanations in the verbosity FAQ, agent activity tracking, statusline setup, custom columns, and hook ordering. Keep setup commands, template namespaces, and hook failure and ordering rules; update generated references and help snapshots. Validated with the documentation sync test, all 56 help tests, the site build, and an independent review of the served passages. > _This was written by Codex on behalf of max-sixty_ |
||
|
|
fc34f8e375 |
docs: trim repeated explanations across six guides (#4575)
Remove repeated explanations and implementation detail from the merge, shell integration, extending, LLM commits, approvals, and tether guides. Keep the usage examples and behavioral distinctions, and update generated references and help snapshots. Validated with the documentation sync test, all 56 help tests, and the documentation site build. Reviewed the served passages in context. > _This was written by Codex on behalf of max-sixty_ |
||
|
|
f117827bd0 |
Preserve JSON results and diagnostics on command failure (#4574)
JSON callers can lose useful results or receive an unexplained failure: config show discarded some diagnostics, for-each abandoned its report on preparation errors, and remove returned before emitting completed removals when interrupted. Keep the existing JSON schemas while restoring stderr diagnostics, handling preparation failures through the per-worktree outcome path, and emitting completed removals before propagating interruption. Later worktrees continue after ordinary preparation failures; signals still stop the batch. Validation: 56 focused integration cases passed; all pre-commit checks, documentation builds, and doctests passed. The full local gate recorded ten failures in unchanged shell/signal/process-discovery paths before an app restart interrupted it; full CI remains the merge gate. > _This was written by Codex on behalf of max-sixty_ |
||
|
|
46b2f5f6fd |
docs: trim code signing policy and clarify test signing (#4572)
Cut the code signing policy from 636 to 260 words, keeping the required attribution, roles, privacy statement, and existing section anchors. Remove unsupported claims about Defender and reproducible builds, and describe the workflow's current test certificate and unsigned-release fallback. Validated with the docs sync test, site build, and independent review of the served copy. > _This was written by Codex on behalf of max-sixty_ |
||
|
|
11bf61cf85 |
Trim Try it page to a single introduction (#4571)
Use “Try Worktrunk in a demo shell” as the introduction and remove the remaining explanatory copy and install link. Keep the full-page demo link and Demoshell attribution. Validated with the docs sync test, docs build, pre-commit checks, and rendered copy review. > _This was written by Codex on behalf of max-sixty_ |