From 4ccacd6d28ec77ef315b7c29890f75442edf4b53 Mon Sep 17 00:00:00 2001 From: Alex Harrison Date: Sat, 19 Sep 2026 04:09:55 -0600 Subject: [PATCH] Document released SDK 0.6.0 methods and migration Ci-From: linux --- quickstart.mdx | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/quickstart.mdx b/quickstart.mdx index 870e457..2bd23cb 100644 --- a/quickstart.mdx +++ b/quickstart.mdx @@ -98,11 +98,11 @@ Saturday publishes SDKs for Python and TypeScript: ```bash Python -pip install saturday +pip install 'saturday>=0.6.0' ``` ```bash TypeScript -npm install @saturdayinc/sdk +npm install '@saturdayinc/sdk@^0.6.0' ``` @@ -148,7 +148,9 @@ console.log(result); Both SDKs default to `https://api.saturday.fit` and accept a base URL override (`base_url` in Python, `baseUrl` in TypeScript) for sandbox work. -The calculation examples above use supported SDK methods. [Activity-prescription TypeScript types](https://github.com/SaturdayInc/saturday-node/issues/6) and [AI streaming methods](https://github.com/SaturdayInc/saturday-node/issues/12) still have known alignment gaps; use direct HTTP for those operations. +SDK 0.6.0 aligns prescription, batch, import, pagination, and athlete-settings types with the API while preserving raw response objects. Activity calculations return a tiered envelope; stored-prescription reads return `{prescription, safety}`, not the flat nutrition response above. Safety warnings may be `null`. Existing typed callers should read the migration notes in the [TypeScript SDK](https://github.com/SaturdayInc/saturday-node#readme) or [Python SDK](https://github.com/SaturdayInc/saturday-python#readme). + +AI coaching remains [feature-gated](/guides/feature-gates). With `ai_coach` access, use `ai.createConversationStream` / `ai.sendMessageStream` in TypeScript, or the async context-managed `ai.create_conversation_stream` / `ai.send_message_stream` methods in Python. Consume all events, including safety warnings and errors. These writes are never automatically replayed, and a partial stream is not a complete answer. Legacy AI JSON-write methods fail locally with migration guidance; conversation metadata/history reads remain JSON. The SDK READMEs include executable stream examples and cancellation guidance. ## 3. Read the response