v0.7.0
Only the breaking entries for the interfaces you use apply. An MCP-only integration, for example, does not need the CLI or REST migrations.
Changed
- [CLI] Breaking: CLI users must replace
--unread-onlywith--read false, replace--starred-onlywith--starred true, pass a boolean to--has-attachment, treat--textas literal text, use typed syntax foremails search, and discard existing page tokens; update CLI commands before upgrading (#76) - [MCP] Breaking: MCP clients must replace the
unreadOnlyandstarredOnlysearch arguments withreadandstarred, treatlist_emails.textas literal text, use typed syntax forsearch_emails.query, and discard existing page tokens; update MCP clients before upgrading (#76) - [REST] Breaking: REST clients must replace the
unreadOnlyandstarredOnlymessage query parameters withreadandstarred, treattextas literal text, and discard existing page tokens; update REST requests before upgrading (#76) - Breaking: Custom provider authors must handle
EmailQuery.readandEmailQuery.starredinstead ofunreadOnlyandstarredOnly, treattextas literal text, add the requiredCapabilities.searchfield, and support both values for every advertised boolean filter; update custom providers before upgrading (#76) - [MCP / CLI / REST] Reject unsupported search filters and provider-native queries before CLI, MCP, or REST requests reach a built-in or custom provider (#77)
Added
- [MCP / CLI / REST] Add typed portable search syntax to CLI
emails search, MCPsearch_emails, and the RESTqueryparameter, with parser diagnostics in MCP and REST results (#76) - [MCP / CLI / REST] Apply portable search normalization and capability checks consistently across CLI, MCP, REST, and email providers (#76)
- [MCP / CLI / REST] Add signed, query-bound page tokens that expire after one hour, plus provider-aware filtered pagination with incomplete-page metadata and canonical attachment checks (#76)
Full Changelog: v0.6.1...v0.7.0