Repository navigation
Docs for Lite 2026.10.17, core 0.71.0 and ThinkWatch 3.7.0 - #74
Merged
Merged
Conversation
- Features (en, zh-CN): outbound redaction no longer searches field names, and custom rules leave alone the identifiers a protocol needs (item and call ids, types, roles, tool names, model names); a custom redaction rule matches by Contains (the default) or Regex, with Match case off by default; a log entry gives how a custom rule matches. - Relay guide (en, zh-CN): Match by and Match case in the new-rule step, what redaction no longer searches, and rules saved before 2026.10.17 that need Regex; the guide follows 2026.10.17. - Contributing (en, zh-CN): the contributor license agreement a first pull request asks for. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The configuration reference gains a custom redaction rule's match and case_sensitive keys and says what redaction does not search; the server guide is unchanged. The overview says field names and protocol identifiers are left alone, and the development guide covers the contributor license agreement. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ules - Configuration (en, zh-CN): a custom redaction rule's match (contains by default, or regex) and case_sensitive; the field names and protocol identifiers redaction leaves alone; the security.redact example sets "match": "regex"; rules saved by 3.0 to 3.6 now match as written and ignoring case, and are changed once every replica runs 3.7.0; old redaction patterns convert to case-sensitive regex rules. - Deployment guide (en, zh-CN): version examples move to 3.7.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Docs for the releases of ThinkWatch Lite 2026.10.17, ThinkWatch Core 0.71.0 and ThinkWatch 3.7.0.
Lite
Core
src/data/core-docsrefreshed from v0.71.0 (CORE_DOCS_REF=v0.71.0 pnpm core-docs):matchandcase_sensitiveonsecurity.redact.custom[], and what redaction does not search. The server guide is unchanged.ThinkWatch 3.7.0
match(containsby default, orregex) andcase_sensitiveon custom redaction rules; the field names and identifier keys redaction leaves alone; thesecurity.redactexample now sets"match": "regex", since without it the pattern would be matched literally; rules saved by 3.0 to 3.6 now match as written and ignoring case, and should be changed only once every replica runs 3.7.0; old pre-3.0 redaction patterns convert to case-sensitive regex rules.pnpm buildpasses.🤖 Generated with Claude Code