Skip to content

v0.4.1: Delete confirmations bound to the asking caller

Latest

Choose a tag to compare

@cyanheads cyanheads released this 07 Oct 12:03
v0.4.1
868b6e6

Delete confirmations bound to the asking caller

  • Delete confirmations are bound to the caller who was asked: an answer from a different tenant, client, or subject is refused as confirmation_invalid and deletes nothing
  • @cyanheads/mcp-ts-core ^0.13.6 → ^0.13.13: error results end with request <id> and carry data.requestId (cyanheads/mcp-ts-core 0.13.10); argument rejections name the field path (0.13.9); error data no longer carries stack traces or request context (0.13.7, 0.13.8) or rootCause (0.13.13); ctx.inputs keeps only answers the client's declared capabilities cover (0.13.10)
  • Docker image installs dependencies in a build-platform deps stage and drops musl-only bindings; server.json npm entries drop the run start:* arguments, and the streamable-http entry sets MCP_TRANSPORT_TYPE=http
  • Dependencies: @biomejs/biome 2.5.14 → 2.5.15, @socketsecurity/bun-security-scanner ^1.1.2 → ^1.1.3, @types/node 26.6.2 → 26.6.4, @vitest/coverage-istanbul 5.0.1 → 5.0.3, ignore ^7.0.9 → ^7.0.12, tsc-alias ^1.9.5 → ^1.9.7, vitest ^5.0.1 → ^5.0.3; Bun 1.4.0 → 1.4.2

CHANGELOG v0.4.1 · release PR #37