release: 0.1.0-alpha.3

[stainless-app]

Automated Release PR

0.1.0-alpha.3 (2026-07-29)

Full Changelog: v0.1.0-alpha.2...v0.1.0-alpha.3

Features

• add waitForAgentReady helper for agent deployment polling (#9) (48a9366)
• api: include indexing jobs (9b9f776)
• api: manual updates (5618f39)
• api: manual updates (06dce24)
• api: manual updates (f1902bc)
• api: remove inf endpoint env (6c3a74a)
• api: responses (b07a208)
• api: update urls for endpoints (5160e2a)
• knowledge base indexing poller (#14) (04e35f0)
• knowledge-bases: add waitForDatabase polling helper (#8) (12d1af3)

Bug Fixes

• client: avoid memory leak with abort signals (ca552af)
• client: avoid removing abort listener too early (82b3689)
• client: improve parameter names (d7270e4)
• docs/contributing: correct pnpm link command (a17c344)
• docs: remove extraneous example object fields (1eaa98c)
• internal: set inference endpoint URL (2611294)
• internal: update default chat completions endpoint (49a0a0c)
• mcp: correct code tool API endpoint (630724d)
• mcp: return correct lines on typescript errors (c35d0f7)

Chores

• break long lines in snippets into multiline (7d854f0)
• ci: skip lint on metadata-only changes (1450f0a)
• client: do not parse responses with empty content-length (b769165)
• client: fix logger property type (ba0b91b)
• client: restructure abort controller binding (ab12908)
• fix typo in descriptions (3013c92)
• formatter: run prettier and eslint separately (ecf993c)
• formatting fixes (b2388ec)
• internal/client: fix form-urlencoded requests (ff211a6)
• internal: avoid type checking errors with ts-reset (e8fe038)
• internal: codegen related update (29f7706)
• internal: codegen related update (200759f)
• internal: codegen related update (faaff42)
• internal: codegen related update (34d9a70)
• internal: codegen related update (600003a)
• internal: codegen related update (1ca1124)
• internal: codegen related update (dbb66cf)
• internal: codegen related update (0d19438)
• internal: improve import alias names (b385dcf)
• internal: more robust bootstrap script (ef7a88b)
• internal: move stringifyQuery implementation to internal function (5042cb3)
• internal: remove mock server code (caa3b9a)
• internal: tweak CI branches (e1e13d1)
• internal: update actions/checkout version (4443a16)
• internal: update dependencies to address dependabot vulnerabilities (6728544)
• internal: update gitignore (f13993e)
• internal: upgrade babel, qs, js-yaml (44e9f8e)
• internal: upgrade eslint (dda1ff1)
• mcp-server: improve instructions (05f9c0b)
• update mock server docs (026c664)

Refactors

• normalize wait-for implementations (#20) (30419d1)

---

This pull request is managed by Stainless's GitHub App.

The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.

For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.

🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions

[stainless-app]

🧪 Testing

To try out this version of the SDK:

npm install 'https://pkg.stainless.com/s/gradient-typescript/ecf993cea0b0f17d269a9bb6c89b68b4764d8031/dist.tar.gz'

Expires at: Fri, 28 Aug 2026 20:57:59 GMT
Updated at: Wed, 29 Jul 2026 20:57:59 GMT

[semgrep-code-digitalocean]

High severity vulnerability may affect your project—review required:
Line 2397 lists a dependency (js-yaml) with a known High severity vulnerability.

ℹ️ Why this matters

Affected versions of js-yaml are vulnerable to Inefficient Algorithmic Complexity / Uncontrolled Resource Consumption. An attacker can supply a YAML document containing a chain of mappings that each merge the previous one via the merge key (<<), causing js-yaml to spend quadratic CPU time while parsing input whose size grows only linearly, resulting in a denial of service.

References: GHSA, CVE

To resolve this comment:
Check if you are using js-yaml on the CLI.

• If you're affected, upgrade this dependency to at least version 4.3.0 at yarn.lock.
• If you're not affected, comment /fp we don't use this [condition]

💬 Ignore this finding

To ignore this, reply with:

• /fp <comment> for false positive
• /ar <comment> for acceptable risk
• /other <comment> for all other reasons

Questions about this issue? Reach out to Product Security in #prodsec-tools.

_{You can view more details on this finding in the Semgrep AppSec Platform here.}