build(deps): Bump the minor-and-patch group with 3 updates

[dependabot]

Bumps the minor-and-patch group with 3 updates: thiserror, termlens and rand.

Updates thiserror from 2.0.20 to 2.0.21

Release notes

Sourced from thiserror's releases.

2.0.21

• Fix parsing of generic unit variants in display expressions (#459)

Commits

• b1827ee Release 2.0.21
• 58037b5 Merge pull request #459 from dtolnay/turbofish
• f82a0cf Keep track of nested turbofish depth
• 72ea492 Raise required compiler to Rust 1.77
• 72eea0d Resolve io_other_error clippy lint in tests
• 07f09a2 Raise required compiler to Rust 1.74
• 2715388 Update ui test suite to nightly-2026-09-22
• 5a306c7 Update ui test suite to nightly-2026-09-05
• ef9383b Update ui test suite to nightly-2026-08-22
• 8336b84 Update ui tests for version 2.0.20
• See full diff in compare view

Updates termlens from 0.11.2 to 0.11.3

Release notes

Sourced from termlens's releases.

v0.11.3

Changed

• termlens render refuses a second format flag or a second --out, naming the conflict, printing its usage and exiting 2, instead of silently keeping the last one (#450). render --svg --html screen.snap asked for an SVG and got HTML at exit 0; --out first.txt --out second.txt wrote only second.txt and said nothing. This is #364's defect in the other argument position, refused for its reason: in a script the two usually come from two variables, and the loser is the one somebody meant. A repeat of the same flag is refused too. Both spellings of --out count, a refused render creates no file, and one format with one --out behaves exactly as before. Neither form was ever documented — the usage has always read (--svg | --html | …) [--out PATH] — but a script that passed two saw exit 0 and now sees 2.

• The 1.0 readiness criteria are a section of docs/STABILITY.md — "The 1.0 readiness criteria", the seven of #335 verbatim — instead of an issue (#472). #335 closed on 2026-09-16 while the candidate statement in the README, this file and STABILITY.md, and three places in docs/RELEASING.md, still cited it as the live record; all of them now link the section, which is where a criterion is recorded as met.

• skills/termlens/SKILL.md's reference tables: locate has one row instead of two that disagreed, with its accessors and why there is no row() (#459); Screen::visual_bells() and Terminal::frame_timings() have rows (#460); .record_budget(cells) states its unit and its default, 2,000,000 cells (#476). §9b names every render format, not only SVG.

• CONTRIBUTING §3 states the rule the skill gives agents first — no sleep as a wait — and names the suite's two sleeps as its exceptions, each with a comment where it sits saying why (#474).

• docs/LIMITATIONS.md names one more Unix-only assertion: the tab-stop extension a resize performs. ConPTY applies ResizePseudoConsole on its own thread, so a program's output written right after a resize can be laid out at the old width; the stress run for this release caught the test that pins the rule doing exactly that, once in 300 Windows iterations. On Windows, wait for the program's own repaint after resize() before asserting on layout. resize itself is unchanged and still claimed there.

Fixed

• termlens inspect --help documents --, the end-of-options marker it has always accepted (#453). It changes the outcome in exactly one case, a program whose name begins with -, which is the one case where a user could not discover it: the help they were pointed at did not have it. examples/inspect.rs has documented it since 0.9.0; the command now says the same thing, and a test tells a flag-shaped program name from an option by which failure comes back.

... (truncated)

Changelog

Sourced from termlens's changelog.

[0.11.3] - 2026-09-23

Changed

• termlens render refuses a second format flag or a second --out, naming the conflict, printing its usage and exiting 2, instead of silently keeping the last one (#450). render --svg --html screen.snap asked for an SVG and got HTML at exit 0; --out first.txt --out second.txt wrote only second.txt and said nothing. This is #364's defect in the other argument position, refused for its reason: in a script the two usually come from two variables, and the loser is the one somebody meant. A repeat of the same flag is refused too. Both spellings of --out count, a refused render creates no file, and one format with one --out behaves exactly as before. Neither form was ever documented — the usage has always read (--svg | --html | …) [--out PATH] — but a script that passed two saw exit 0 and now sees 2.

• The 1.0 readiness criteria are a section of docs/STABILITY.md — "The 1.0 readiness criteria", the seven of #335 verbatim — instead of an issue (#472). #335 closed on 2026-09-16 while the candidate statement in the README, this file and STABILITY.md, and three places in docs/RELEASING.md, still cited it as the live record; all of them now link the section, which is where a criterion is recorded as met.

• skills/termlens/SKILL.md's reference tables: locate has one row instead of two that disagreed, with its accessors and why there is no row() (#459); Screen::visual_bells() and Terminal::frame_timings() have rows (#460); .record_budget(cells) states its unit and its default, 2,000,000 cells (#476). §9b names every render format, not only SVG.

• CONTRIBUTING §3 states the rule the skill gives agents first — no sleep as a wait — and names the suite's two sleeps as its exceptions, each with a comment where it sits saying why (#474).

• docs/LIMITATIONS.md names one more Unix-only assertion: the tab-stop extension a resize performs. ConPTY applies ResizePseudoConsole on its own thread, so a program's output written right after a resize can be laid out at the old width; the stress run for this release caught the test that pins the rule doing exactly that, once in 300 Windows iterations. On Windows, wait for the program's own repaint after resize() before asserting on layout. resize itself is unchanged and still claimed there.

Fixed

• termlens inspect --help documents --, the end-of-options marker it has always accepted (#453). It changes the outcome in exactly one case, a program whose name begins with -, which is the one case where a user could not discover it: the help they were pointed at did not have it. examples/inspect.rs has documented it since 0.9.0; the command now says the same thing, and a test tells a flag-shaped program name from an

... (truncated)

Commits

• 5830c93 test: wait for the last row painted before masking, and one MSYS exclusion (#...
• bc1a2f8 test: the resize tab-stop rule is Unix-only under ConPTY (#499)
• 37609b7 test: wait for the newline, not the marker, before typing a Tab (#498)
• c15b62f chore: release v0.11.3 (#496)
• 54e4d8d test(ci): hold the published binary to both trailers and every = spelling (#495)
• 73266e4 docs: the 1.0 criteria in STABILITY.md, and the skill tables caught up (#492)
• 47bf4f9 fix(cli): a bare termlens - is still an unknown command (#494)
• ff0e070 fix(cli): refuse a second render format or --out, and document inspect -- (#489)
• ce61e56 test(ci): add a DCO gate selftest (#493)
• 0c8e4c1 fix(cli): start inspect's silence window at the first output, not the spawn (...
• Additional commits viewable in compare view

Updates rand from 0.10.2 to 0.10.3

Changelog

Sourced from rand's changelog.

[0.10.3] — 2026-09-20

Fixes

• Fix WeightedIndex panic when the sum of float weights is infinite; return Error::Overflow instead (#1808)
• Fix spurious Error::NonFinite from Uniform::new_inclusive on large finite float ranges such as 0.0..=f64::MAX (#1821)
• Fix possible panic due to sampling a deserialized Uniform<char> (#1831)

Changes

• Report exact remaining lengths from WeightedIndex::weights() and reduce overhead when reading weights (#1838)

#1808: rust-random/rand#1808 #1821: rust-random/rand#1821 #1831: rust-random/rand#1831 #1838: rust-random/rand#1838

Commits

• 9e7d328 Prepare rand 0.10.3 (#1840)
• f73ce74 Optimize WeightedIndex weight lookup and iteration (#1838)
• ef9e044 Avoid panic from deserialized Uniform\<char> where range == 0 (#1831)
• c994eb1 docs: fix angle unit in quick start example (#1839)
• 33dea4f Test that WeightedIndex rejects INFINITY with Error::Overflow (#1822)
• 94c9078 Fix Uniform::new_inclusive overflow on large finite float ranges (#1821)
• bb1262f Use Xoshiro256PlusPlus in examples/rayon-monte-carlo.rs (#1805)
• 521fab6 Stop pinning dependencies (#1820)
• 3f7c433 Stop pinning dependencies
• cf4f73e sample_efraimidis_spirakis: error on more than amount non-finite weights (#1814)
• 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.