v1.13.2

v1.13.2 — Patch: the desktop extension boots again

If you installed the v1.13.0 or v1.13.1 .dxt in Claude Desktop, it crashed on startup — silently. This release fixes the packaging bug and adds a CI gate so it can't recur. Env-based and clone-based setups were never affected.

What happened

An unanchored src/ pattern in .dxtignore (gitignore semantics match at any depth) stripped node_modules/debug/src/ from the packed archive — the entry point of a runtime dependency loaded at startup. The server process died ~170 ms after initialize with nothing on stderr; the only trace was an import-failed line in Claude Desktop's main.log.

Changes

• .dxtignore patterns are now root-anchored, with the failure documented in-file.
• The release workflow now boots the exact packed artifact (unpack → MCP initialize → require a response) before anything is published — a broken .dxt can no longer ship.
• Dev dependencies are pruned from the archive (typescript/tsx/@types no longer bundled; ~12% fewer files).

Upgrading

Download fastmail-mcp-1.13.2.dxt below and reinstall the extension in Claude Desktop. Your configured settings are preserved. If tools then report authentication errors, your configured API token or app password may have been rotated — mint fresh credentials in Fastmail Settings → Privacy & Security and update the extension config.

---

This is an unofficial community project, not affiliated with, endorsed by, or supported by Fastmail.

Full Changelog: v1.13.1...v1.13.2