6b5aad0600962e0988c1b86951e14d52639fdb77, recorded in scripts/docs-release.json and tagged v4.11.0.
Follow installation to install matching package versions. Downloadable projects target the matching 4.11.0 GitHub release. Use matching locally packed packages for SDK development and retain the source revision with your test results.
Choose your upgrade path
What 4.11 adds
OpenAI Decisions accepts native JSON evidence, hosted images, real conversation roles, paired tool history, text/image questions, and explicit prompt-cache controls. Existing Agent question and answer shapes remain supported. Use the concreteOpenAIDecisionsProvider class for native evaluate() calls.
Gemini Argon adds model-family request controls through the existing Google SDK transport. Signed function-call history and model identities survive terminal stream chunks. A response requiring unsupported continuation fails with usage retained.
Cost accounting separates Decisions ordinary input, cache reads, and cache writes, and adds reviewed Sol Ultrafast Responses and Gemini Argon GenerateContent tariffs. Missing counters and unsupported billing dimensions stay incomplete. Historical assessments are unchanged.
Review compatibility changes
Decisions now preserves real roles instead of text labels, which can change classifications. Recheck representative examples and thresholds. Corrected cache accounting can change estimated totals. Review Argon reasoning, caching, and output limits before selecting it. The 4.11 upgrade guide explains each change.Earlier minor releases
4.10 adds pinned skill snapshots, opt-in native decision journaling and application-state recovery, and Google/Ollama request controls. 4.9 adds Workflow dependency graphs, opt-in recoverable execution graphs, bounded planning, and evidence-backed continuity. 4.7–4.8.3 add local EmbeddingGemma 2 multimodal embeddings. See what’s new, the historical 4.9 compatibility guide, and the SDK changelog.What verification establishes
Docs checks validate content synchronization, navigation, internal links, public imports and complete TypeScript examples. Generated references cover every public harness export and core-root/transport/queue export in their declared scope. Credential-free recipes execute the local harness, HTTP ownership, evaluation success/failure, simulated telephony and graph result-reuse paths. The release separately verifies registry metadata, served tarball integrity and installed package consumers against retained release artifacts. Docs checks do not establish live-provider quality, distributed failover, production speed or deployment status. The SDK retains separate source-suite, packed-consumer and disposable-backend evidence. Your persistent store, connector reconciliation, device/carrier and cloud deployment still need integration-specific validation. Unknown usage remains unknown; offline fixture tokens and latency are not vendor billing or production-performance measurements. Maintainers runnpm run check:release to verify exact public metadata for all ten packages. That check does not download, install or execute the packages; tarball integrity and installed-consumer validation remain separate release gates.