build(deps): Bump vyncint/termlens/.github/actions/report from 0.11.5 to 0.11.6

[dependabot]

Bumps vyncint/termlens/.github/actions/report from 0.11.5 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?".

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]

[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

... (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)
• See full diff 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 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)