Caller cancellation, mcp-ts-core ^0.12.5
- A caller that disconnects mid-request now surfaces
RequestCancelledimmediately instead of being retried, or walked one ID at a time in the batch-results fallback @cyanheads/mcp-ts-core^0.12.3 → ^0.12.5 — upstream 500/501 responses classify asServiceUnavailable, a disconnected client reports as a cancellation, and server identity resolves from the served package rather than the working directory- SSRF DNS guard (inherited from the framework bump) now queries both Node resolvers, closing a path where a system-resolver-only hostname passed the check
.env.examplesession mode now matches the Dockerfile'sstatelessdefault (#115)- Skill library resync (10 skills) and toolchain dependency refresh
deps: zod ^4.4.3 → ^4.5.4 (+ dev-dep bumps)