v1.1.0
mail-index v1.1.0
First feature release since 1.0.0. All changes are additive and backward-compatible — the local index auto-migrates on next open (schema v6 → v7).
✨ Auto-update (new)
From this version on, mail-index keeps itself up to date. On launch, the CLI/MCP fire a background check against the npm registry; when a newer version is published, the install updates itself and the new build is picked up on the next launch.
- Non-blocking & safe: the check runs detached and never delays startup. An update is never hot-swapped into a running process — a long-lived MCP server keeps serving its loaded build until it next restarts, so the CLI and MCP always stay in lockstep on one install.
- Throttled: at most once per 24h.
- Opt-out: set
MAIL_INDEX_NO_AUTOUPDATE=1to disable entirely. - Install-aware: an npm-global install updates with
npm i -g mail-index@latest; a git checkout fast-forwardsmainand rebuilds (only when the checkout is clean — your work is never clobbered). - Privacy preserved: the updater is quarantined in
bin/(the one network seam besides the provider adapter) so the core (src/) stays provably egress-free — enforced by the same CI egress guard, which now auditsbin/too. See THREAT-MODEL / SECURITY.
🧭 Deterministic correspondent cadence (new)
mail-index cadence --account <a> [--category <c>] [--since <30d|1mo>] and a matching cadence MCP tool: how often each sender brand emails you (volume, distinct senders, first/last, per-month), groupable by an agent-assigned entity category. Brands are keyed by a new registrable-domain (eTLD+1) normalization (domains.registrable_domain, migration m006).
🔎 FTS improvements
- m005: repaired FTS schema drift (rebuilds
messages_ftsto the canonical 4-column, rowid-aligned shape) — fixes wrong-result rows on indexes created by the pre-v1 prototype. - m007: porter-stemmed FTS contract with bm25 weighting + query expansion for better recall.
Upgrade
npm i -g mail-index@1.1.0 (or just let auto-update handle it), or download the attached .mcpb.