Skip to content

v0.17.1

Latest

Choose a tag to compare

@steipete steipete released this 16 Nov 06:24
· 1 commit to main since this release
v0.17.1
0d8ccc9

Highlights: Keep the daemon available after a refused stop, improve OAuth credential handling and CLI argument fidelity, and patch six development dependency security advisories.

  • Keep the daemon serving after an upfront stop refusal and track owned descendants beneath verified foreign-owned helpers. Thanks @zm2231 (#498).

  • Use portable per-column process inventory arguments on BSD systems so daemon transport ownership can be verified. Thanks @e4779 (#499).

  • Wait for all OAuth cache operations to finish before reporting a failure, preventing delayed writes from racing cleanup or subsequent requests.

  • Keep server proxies non-thenable so awaiting them or returning them from async functions cannot dispatch an unintended then tool call. Thanks @JYunth (#503).

  • Use cached OAuth credentials when a resolved static Authorization header is empty, preserving valid static credentials and required environment validation. Thanks @koinzhang (#506, #505).

  • Preserve parsed call arguments when referenced or unconstrained schema branches may accept their type, while respecting explicit type exclusions. Thanks @HengYangDS (#501).

  • Preserve leading and trailing whitespace in string call arguments, including when coercion is disabled. Thanks @JYunth (#504).

  • Preserve quoted empty arguments in ad-hoc stdio commands and reject an empty executable in stdio and generated CLI commands. Thanks @SebTardif (#497).

  • Apply the documented server-name correction and suggestion rules to auth, keeping unknown names actionable and diagnostics off JSON stdout. Thanks @KrasimirKralev (#500).

  • Report remaining CLI argument errors once without internal stack traces, preserving messages, exit codes, and runtime diagnostics. Thanks @KrasimirKralev (#495).

  • Patch six Hono and Node adapter security advisories in development fixtures; refresh runtime helpers, bundling, and lint tooling while preserving Node 24 support, the 48-hour dependency cooldown, and existing security overrides.

Verification: npm, registry tarball, release CI, release rehearsal, and native assets. npm integrity: sha512-ukSt7Vjdw3h+7262yRzJ6o9kUcEszvmnKDnxxMgFujD7vcvIOrRo5UjXn8/TAGRP8NbrA4dzsawJG++xQxuW+g==.