build(deps): bump the cargo-minor-patch group across 1 directory with 3 updates

[dependabot]

Bumps the cargo-minor-patch group with 3 updates in the / directory: serde_json, libc and termlens.

Updates serde_json from 1.0.151 to 1.0.154

Release notes

Sourced from serde_json's releases.

v1.0.154

• Support preserve_order in no_std builds (#1333, thanks @​razmser)

v1.0.153

• Report invalid UTF-8 at the first bad byte (#1345, thanks @​00200200)

v1.0.152

• Preserve sign of -0 in arbitrary_precision mode (#1346, thanks @​yuxi-liu-wired)
• Fix comparison of large non-integer values with f32::INFINITY (#1347, thanks @​yuxi-liu-wired)

Commits

• 20572a6 Release 1.0.154
• a91bfaf Fix RandomState links in map documentation
• 3c932c0 Merge pull request #1333 from razmser/no-std-preserve-order
• 4b2d726 Release 1.0.153
• 83335ee Touch up PR 1345
• 4b4810a Resolve range_plus_one pedantic clippy lint
• 8af71cc Merge pull request #1345 from 00200200/fix-invalid-utf8-error-column
• 452afa2 Correct multiline raw UTF-8 error positions and simplify indexing
• c9f1e3b Release 1.0.152
• 854fc70 Touch up PR 1347
• Additional commits viewable in compare view

Updates libc from 0.2.189 to 0.2.190

Release notes

Sourced from libc's releases.

0.2.190

There is now a single config for enabling 64-bit time_t: libc_unstable_time64. This can be set unconditionally; it opts in to 64-bit time_t on the following platforms that use 32-bit by default:

• 32-bit Linux-GNU
• 32-bit Linux-uClibc
• 32-bit Linux-musl. Note that setting this flag also enables some other changes that happend in musl v1.2.
• 32-bit Windows-GNU
• ESP-IDF (all targets with this environment are 32-bit)

Most other 32-bit platforms are either already using 64-bit time_t, or are considered legacy and will not be gaining support from their upstream maintainers.

You can enable this using RUSTFLAGS:

RUSTFLAGS='--cfg=libc_unstable_time64' cargo ...

Note that there may still be some changes to features gated by this config option, hence "unstable" in its name. In the near future we will rename it to just libc_time64. Until then, please test it out and report any bugs you find!

Support

• Add initial support for HelenOS (#4355)

Added

We are slowly filling out the Default implementations, to reduce the need for mem::zeroed() in user code:

• Unix: Implement Default for a number of structs, especially on Apple platforms (#5576)
• Linux, NetBSD: Give statvfs a Default impl (#5583)
• Linux: Add Default to a linux/can.rs structs (#5257)

Other additions:

• Expose the libc_unstable_time64 cfg (#5411)
• Android, Glibc: Add pthread_gettid_np (#5359)
• Android: Add RTLD_NEXT (#5323)
• Android: Add reuseport BPF socket options (#5366)
• Apple: Add TCP header flags, options and SACK limits (#5358)
• Apple: Add NET_RT_DUMP2 (#5442)
• Apple: Add posix_spawn_file_actions_add(f)chdir(_np) (#5558)
• BSD: Add BPF_WORDALIGN (#5320)
• BSD: Add lchmod and lchflags where supported (#5400)
• BSD: Add minherit and related constants (#4849)
• Docs: Add more links to public headers and manual pages (#5407), (#5485)

... (truncated)

Changelog

Sourced from libc's changelog.

0.2.190 - 2026-10-02

There is now a single config for enabling 64-bit time_t: libc_unstable_time64. This can be set unconditionally; it opts in to 64-bit time_t on the following platforms that use 32-bit by default:

• 32-bit Linux-GNU
• 32-bit Linux-uClibc
• 32-bit Linux-musl. Note that setting this flag also enables some other changes that happend in musl v1.2.
• 32-bit Windows-GNU
• ESP-IDF (all targets with this environment are 32-bit)

Most other 32-bit platforms are either already using 64-bit time_t, or are considered legacy and will not be gaining support from their upstream maintainers.

You can enable this using RUSTFLAGS:

RUSTFLAGS='--cfg=libc_unstable_time64' cargo ...

Note that there may still be some changes to features gated by this config option, hence "unstable" in its name. In the near future we will rename it to just libc_time64. Until then, please test it out and report any bugs you find!

Support

• Add initial support for HelenOS (#4355)

Added

We are slowly filling out the Default implementations, to reduce the need for mem::zeroed() in user code:

• Unix: Implement Default for a number of structs, especially on Apple platforms (#5576)
• Linux, NetBSD: Give statvfs a Default impl (#5583)
• Linux: Add Default to a linux/can.rs structs (#5257)

Other additions:

• Expose the libc_unstable_time64 cfg (#5411)
• Android, Glibc: Add pthread_gettid_np (#5359)
• Android: Add RTLD_NEXT (#5323)
• Android: Add reuseport BPF socket options (#5366)
• Apple: Add TCP header flags, options and SACK limits (#5358)
• Apple: Add NET_RT_DUMP2 (#5442)
• Apple: Add posix_spawn_file_actions_add(f)chdir(_np) (#5558)
• BSD: Add BPF_WORDALIGN (#5320)
• BSD: Add lchmod and lchflags where supported (#5400)
• BSD: Add minherit and related constants (#4849)

... (truncated)

Commits

• 7b0ab55 ci: Rename publish_0.2.yml to release.yaml
• ac85dde ci: Sync release permissions with main
• 8f8cd20 libc: Release 0.2.190
• 052c6e6 changelog: Fix an incorrect commit link
• ea19fd7 test: Remove explicit libc version
• 6dbf3a2 dragonfly: Move INHERIT_ZERO to the freebsd module
• 8a64766 apple: add posix_spawn_file_actions_add(f)chdir(_np)
• 28de514 linux, netbsd: Give statvfs a Default impl
• a58a95f cygwin: Change POSIX_SPAWN_* flags to c_short
• d175264 apple: timeval32 is exhaustive
• Additional commits viewable in compare view

Updates termlens from 0.11.4 to 0.11.6

Release notes

Sourced from termlens'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 termlens's changelog.

[0.11.6] - 2026-10-14

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?".

[0.11.5] - 2026-10-07

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,

... (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

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