Unverified50% confidenceDecision RuleExact time
The article suggests: if a project is calling the Responses API via Vertex AI, using Realtime WebSocket and encountering issues such as lost close state after connection recovery or connections not being properly released after cancellation, or still relying on Pydantic v1 for request validation, it should upgrade to v3.36.0 as soon as possible.
1
Sources
50%
Confidence
Short-term (~14 days)
Relevance
10/21/2026
First Seen
Valid until: 11/4/2026
Sources
Related Entities
Related Claims
UnverifiedIf a project is pinned to an older websockets version and does not have Realtime enabled, the v3.35.1 update has limited impact on existing behavior.70% similarUnverifiedv3.36.0 concentrated on fixing multiple boundary issues related to Realtime WebSocket, including cleanup of failed connection establishment, respect for native options, ending sync WebSocket recovery on interruption, respecting Translation receipt with timeout during terminal cleanup, preserving WebSocket close state across recovery and cancellation scenarios, and respecting native options for the legacy beta socket (PR #4121, #4129, #4132, #4117, #4120).64% similarUnverifiedv3.32.0 declared Realtime response error messages (PR #4083), filling the gap in error feedback for the real-time interface.62% similarUnverifiedProjects still relying on the legacy completions endpoint should migrate to the Chat Completions or Responses API as soon as possible to avoid future compatibility issues.62% similarUnverifiedv3.30.0 supports updating the expiration time of project API keys, allowing the expiration policy to be adjusted without recreating the key.61% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1081995API
curl https://kongchang.com/api/v1/knowledge/claims/1081995MCP
get_claim(id=1081995)