[dependabot]

Bumps the actions-minor-patch group with 3 updates in the / directory: Swatinem/rust-cache, vyncint/termlens/.github/actions/report and rust-lang/crates-io-auth-action.

Updates Swatinem/rust-cache from 2.9.2 to 2.9.3

Release notes

Sourced from Swatinem/rust-cache's releases.

v2.9.3

What's Changed

• Issue-375: stop cleanup timestamp pruning after the first entry by @​TethysSvensson in Swatinem/rust-cache#377
• fix: log rustup toolchain list failure as info instead of warning by @​SDAChess in Swatinem/rust-cache#394

New Contributors

• @​TethysSvensson made their first contribution in Swatinem/rust-cache#377
• @​SDAChess made their first contribution in Swatinem/rust-cache#394

Full Changelog: Swatinem/rust-cache@v2.9.2...v2.9.3

Changelog

Sourced from Swatinem/rust-cache's changelog.

Changelog

2.9.3

• Fix timestamp based pruning
• Add missing awaits
• Do not emit warning on missing rustup

2.9.2

• Fix credentials.toml cleanup
• Improvements to cleanup, preserving more valid targets
• Improvements to cargo install handling
• Correctly sort/dedupe Rust versions

2.9.1

• Fix regression in hash calculation

2.9.0

• Update to node24
• Support running from within a nix shell
• Consider all installed toolchains for cache key
• Use case-insensitive comparison to determine exact cache hit

2.8.2

• Don't overwrite env for cargo-metadata call

2.8.1

• Set empty CARGO_ENCODED_RUSTFLAGS when retrieving metadata
• Various dependency updates

2.8.0

• Add support for warpbuild cache provider
• Add new cache-workspace-crates feature

2.7.8

• Include CPU arch in the cache key

2.7.7

• Also cache cargo install metadata

2.7.6

... (truncated)

Commits

• d1527c8 2.9.3
• f0fca6f update dependencies and rebuild
• b49b17f add missing awaits
• 6a7bc3e Bump the dev-minor group across 1 directory with 2 updates (#383)
• 4ece996 Bump the actions group across 1 directory with 6 updates (#392)
• 8103aff Bump the prd-minor group across 1 directory with 2 updates (#389)
• 0e361f3 fix: log rustup toolchain list failure as info instead of warning (#393) (#394)
• f0d9c38 Merge pull request #380 from Swatinem/dependabot/github_actions/actions-8ff58...
• ccd9742 Bump the actions group with 2 updates
• 258712b fix: stop cleanup timestamp pruning after the first entry (#377)
• Additional commits viewable in compare view

Updates vyncint/termlens/.github/actions/report from 0.11.4 to 0.11.6

Release notes

Sourced from vyncint/termlens/.github/actions/report's releases.

v0.11.6

Fixed

• On Unix, a program that exists but cannot be executed now fails TerminalBuilder::spawn with an Error::Spawn that says why, and termlens inspect exits 2 with that message (#563). Typical causes are a missing #! interpreter, an interpreter that is not a program, a missing dynamic loader, and an argument list over the kernel's limit. The message names the interpreter, with any \r that CRLF line endings left on it shown escaped. spawn used to return Ok with a child already killed by SIGABRT (fatal runtime error: assertion failed: output.write(&bytes).is_ok()), which inspect showed as exited: killed by signal: Aborted. portable-pty closed the pipe std reports a failed exec through, so on Unix termlens now starts the child itself. Program resolution, the environment, the session and the signals are unchanged, and the child still inherits no descriptor besides its terminal. A working directory the child cannot enter is now named in the error. A few rare setups are still left to portable-pty, as before, and docs/DESIGN.md lists them.
• The second writer termlens opens on the PTY master is close-on-exec. A process the test started while a terminal was alive inherited it before, which kept the master open in a process unrelated to the terminal.
• With TERM set twice through .env, XTGETTCAP's TN reply reports the later value, the one the child gets. It reported the first, so an application could get two answers to "which terminal is this?".

v0.11.5

Changed

• The documentation was reviewed against the code, and each correction was checked by reading the code or running it:
  • README.md and the skill recommend cargo install termlens-cli --locked, the dependency set a release is tested with (#552), and AGENTS.md's layout lists the termlens-cli crate (#553).
  • The skill's rule 9 gives the true reason to return termlens::Result: a failing test prints the error's Debug form, screen included, as unwrap() would. §6 now reads that form as well as Display, and its unanswered-probe row links to docs/LIMITATIONS.md (#559). Rule 10, §6 and the mask row no longer say that format!("{:?}") equals Display, that every error carries a screen, or that mask_matching matches across a soft wrap (#562).
  • The rustdoc gains runnable examples for Screen::mask_matching (#551) and ScreenDiff::changed_rows and style_changes (#560). On docs.rs, Unsupported no longer shows Clipboard's summary, and Clipboard has one of its own (#562).
  • docs/DESIGN.md, CONTRIBUTING.md, docs/RELEASING.md, docs/LIMITATIONS.md and SECURITY.md now match the code. They cover the two translated character sets and DECSC saving the charset state, the SHELL=/bin/sh pin under env_clear, the tools/ directory, and the release checklist's two ungated copies of the version (#558). They

... (truncated)

Changelog

Sourced from vyncint/termlens/.github/actions/report's changelog.

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

0.11.0 is the stability candidate: from that release no promised item changes incompatibly before 1.0. A change that must break one ships as a new candidate (0.12.0) with a migration table and restarts the observation window of the 1.0 readiness criteria; a patch release does not. 1.0 follows those criteria, not a date.

A breaking change is always listed under a Changed or Removed heading, in a bullet that begins Breaking: — the semver gate in CI reads that marker.

[Unreleased]

Fixed

• termlens no longer panics with exit code 101 (#594). A closed or full stderr (2>&1 | true, 2>/dev/full) made every diagnostic and the inspect trailer panic; the write is now checked, and a trailer that cannot be written is exit 2. Arguments are read with args_os, so one that is not UTF-8 no longer panics: termlens's own options and operands are refused with exit 2, and the program inspect runs gets its arguments untouched. A --timeout too large to add to the clock is refused by name instead of panicking after the spawn, and render --out "" says --out needs a PATH argument as --out= already did (#451). The inspect example mirrors all of it, --help under | true included.
• Screen::parse and the JSON reader refuse a saved screen whose declared size is past the 1000-per-axis limit a terminal has (#583), with an Error::Parse that names it. The grid was allocated from the header before any line was read, so a 31-byte file declaring 65535x65535 made termlens render try to allocate 206 GB and abort. No termlens ever wrote a screen that large.
• A coloured termlens diff no longer takes time quadratic in the number of changed cells (#595). Painting checked each cell against the whole list of changed cells, so a full-screen change on a large terminal took seconds (8 s at 80,000 cells). The changed cells are now collected once.
• Screen::to_svg draws an underlined or struck-through run of blanks, such as an empty form field, with its line (#586); it trimmed the run to nothing and dropped it. The trailing blanks of any underlined or struck-through run are now drawn with the line too, as in to_html. to_svg and to_html also write a character XML 1.0 forbids, a C0 control other than tab, LF and CR or U+FFFE/U+FFFF, as U+FFFD, so a window title holding \x01 or a cell holding U+FFFF no longer makes an SVG no parser opens.

[0.11.6] - 2026-10-14

... (truncated)

Commits

• 3926896 chore: release v0.11.6 (#572)
• 83c6a10 fix: report an exec failure as a spawn error, not a SIGABRT child (#566)
• e375c9d chore(deps): bump the cargo-minor-patch group across 1 directory with 3 updat...
• 459ef26 chore(deps): bump the actions-minor-patch group across 1 directory with 2 upd...
• 13b397b chore(deps): bump dtolnay/rust-toolchain (#569)
• 9bcc3fa ci: repin dtolnay/rust-toolchain to where v1 points now (#567)
• 093544f ci: move the semver baseline to v0.11.5 (#565)
• 5b6bf71 chore: release v0.11.5 (#564)
• 5f4203e fix: a relative current_dir runs a relative program, and inspect's help says ...
• a9edfe7 docs: a review pass, fifteen claims the code contradicts (#562)
• Additional commits viewable in compare view

Updates rust-lang/crates-io-auth-action from 1.0.5 to 1.0.6

Release notes

Sourced from rust-lang/crates-io-auth-action's releases.

v1.0.6

What's Changed

update dependencies

Full Changelog: rust-lang/crates-io-auth-action@v1.0.5...v1.0.6

Commits

• 3268eb4 Merge pull request #278 from marcoienibot/chore/update-dependencies-2026-10
• e901356 chore(deps): update dependencies and GitHub Actions
• 9c067fc Merge pull request #277 from rust-lang/renovate/msw-3.x
• 9b55005 chore(deps): update dependency msw to v3
• 4920f09 Merge pull request #276 from rust-lang/renovate/major-github-actions
• 04dcccb chore(deps): update github actions
• 82864bf Merge pull request #274 from rust-lang/renovate/major-vitest-monorepo
• 2bd8e07 chore(deps): update dependency vitest to v5
• f14f407 Merge pull request #271 from rust-lang/renovate/github-actions
• 0205d6c chore(deps): update github actions
• Additional commits viewable in compare view

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 commands and options

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

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.