docs: document 0.17.0 release#435
Merged
Merged
Conversation
0.17.0 added several user-facing surfaces that were only partially covered by the existing site. Capture the release notes and bring the public docs in line with the actual CLI, API, config, and daemon behavior so users can discover backup, Teams sync, message-type filtering, scoped embeddings, and the daemon-era changes from one place. The Teams guide and expanded references spell out the concrete command flags, token locations, scheduler behavior, and API filters verified against the implementation, while the changelog credits contributors from the release PRs. Generated with Codex Co-authored-by: Codex <codex@openai.com>
roborev: Combined Review (
|
- MCP search_messages/list_messages have no message_type parameter; scoping goes through the message_type: query operator, and only find_similar_messages takes a dedicated parameter - get_message windowing pages the response body, it does not bound server memory; document the actual paging parameters - Scheduled [[gcal]] syncs bypass the run_after_sync embed hook; calendar events are embedded via the embed worker cron instead - backup init does not persist [backup].repo, so quick-start examples now pass --repo explicitly and point to the config key Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
GetGmailIDsByFilter only applies sender/sender_name, recipient/ recipient_name, domain, label, source_id, and limit; it is hardwired to Gmail sources, always excludes deleted messages, and ignores the other /messages/filter parameters. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
roborev: Combined Review (
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
0.17.0 shipped a broad set of user-facing surfaces, and the existing docs only covered part of the release. The release notes and docs need to match the implementation so users can discover backup, Teams sync, message-type filtering, scoped embeddings, and the daemon/API changes from the public site.
What changed
Validation
make docs-checkDeploy
Docs deployment is manual after merge: run
make docs-deploy(or the project's docs deploy flow) so the public site picks up the release docs.