---
summary: "A 501 from NWS now fails fast instead of retrying, a caller disconnect classifies as RequestCancelled instead of Timeout, server identity no longer depends on the caller's working directory, and new dependency overrides clear 6 transitive fast-uri and qs advisories. mcp-ts-core moves ^0.12.3 to ^0.12.5."
breaking: false
security: true
---

# 0.9.2 — 2026-09-04

## Changed

- **The local 500/501 → `ServiceUnavailable` override is gone** — `@cyanheads/mcp-ts-core` 0.12.4 classifies the whole 5xx range that way itself, so the server's own `codeOverride` on `httpErrorFromResponse` was redundant and is removed.
- **Server identity no longer depends on the caller's working directory** (mcp-ts-core 0.12.5 `resolveAppRoot()`) — verified on the wire: `initialize` returns the correct `serverInfo` name and version regardless of the launching client's cwd.
- Framework skills (`skills/`) re-synced to the versions shipped with `mcp-ts-core` 0.12.5.

## Fixed

- **A 501 fails fast instead of retrying** — mcp-ts-core 0.12.4 marks it `data.retryable: false` in-band; `isRetryableNwsError` now honors the flag, so a method NWS will never implement stops burning three retry attempts. A 500 is unchanged — still `ServiceUnavailable`, still retried.
- **A caller disconnect classifies as `RequestCancelled` (-32011)** instead of a bare abort that downstream classification read as `Timeout` — fixed at two call sites in `nws-service.ts`: the initial fetch, and a retry backoff sleep where the abort previously bypassed the classification path entirely. Unit-tested; under this server's `MCP_SESSION_MODE=stateless`, a client hangup does not propagate a cancellation signal into the in-flight handler, so this is not yet observable on the wire.
- **Multi-arch Docker publish no longer fails on an arm64 host** ([cyanheads/mcp-ts-core#370](https://github.com/cyanheads/mcp-ts-core/issues/370)) — the build stage is pinned to `$BUILDPLATFORM`, so the `linux/amd64` leg cross-compiles instead of running under QEMU, where bun >= 1.4 aborts and no image publishes for either architecture.
- README `MCP SDK` badge corrected `^1.30.0 → ^2.0.0` — stale since the framework adopted SDK v2 in 0.9.1.

## Security

- **6 transitive advisories cleared** — a new `overrides` block pins `fast-uri` `^3.1.6` and `qs` `^6.16.0`, closing 4 high-severity `fast-uri@3.1.5` advisories (GHSA-5jgf-p345-68v8, GHSA-f65p-4m7j-42xc, GHSA-fph4-wmhf-6fwf, GHSA-jqff-g426-hqxp — host confusion/SSRF) and 2 moderate `qs@6.15.3` advisories (GHSA-x5fp-wj9c-mxmx, GHSA-4mjr-xmp4-gh2g) reaching in transitively through `@cyanheads/mcp-ts-core > @modelcontextprotocol/ext-apps > @modelcontextprotocol/sdk`. `bun audit` now reports no vulnerabilities across 372 packages.

## Dependencies

- `@cyanheads/mcp-ts-core` `^0.12.3 → ^0.12.5`
- `zod` `^4.4.3 → ^4.5.4`
- `@biomejs/biome` (dev) `^2.5.10 → ^2.5.11`
- `@types/node` (dev) `^26.2.0 → ^26.4.0`
- `ignore` (dev) `^7.0.6 → ^7.0.8`
- `tsc-alias` (dev) `^1.9.2 → ^1.9.3`
- `fast-uri` (override, new) `^3.1.6`
- `qs` (override, new) `^6.16.0`
