Manual Release - 2026-08-31 - #12
Conversation
Greptile SummaryThis manual release publishes version 3.5.0 with regenerated protocol types, a new assistant action, revised build artifacts and integrations, and mandatory outbound privacy validation.
Confidence Score: 4/5The release should not merge until mandatory privacy validation stops rejecting legitimate descriptive metadata and reference values. Every outbound send now applies a coarse length-and-punctuation heuristic to free-form fields, causing schema-valid customer payloads to be dropped as privacy violations. Files Needing Attention: sdks/javascript/runtime/validation/pi-guard.js, sdks/javascript/runtime/core/main.js Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[Application calls send or action helper] --> B[Build outbound payload]
B --> C{strictValidation enabled?}
C -->|Yes| D[Schema validation]
D --> E[Privacy guard]
C -->|No| E
E --> F{Long multiline or punctuated string?}
F -->|Yes| G[PAYLOAD_SCHEMA_MISMATCH]
F -->|No| H[Send over WebSocket]
Reviews (1): Last reviewed commit: "chore(release): promote SDK changes to p..." | Re-trigger Greptile |
| if (trimmed.includes('\n') && trimmed.length > 40) return true; | ||
| if (trimmed.length > 160 && /\s/.test(trimmed) && /[.!?]/.test(trimmed)) return true; |
There was a problem hiding this comment.
Privacy heuristic rejects valid metadata
When custom metadata, labels, or tags contain multiline text longer than 40 characters or ordinary punctuated prose longer than 160 characters, looksLikeMessageContent marks the schema-valid value as prohibited content, causing every outbound send to abort with PAYLOAD_SCHEMA_MISMATCH even when strict validation is disabled.
Manual Release
Version: 3.5.0
Source: main
Target Environment: Public Production
Target Repository: optave/interface-client-sdk-lib-dist
Triggered by: ndovha
Files Published:
Validation Completed:
Ready for review and merge to main.