release: 0.38.0

[stainless-app]

Automated Release PR

0.38.0 (2026-03-10)

Full Changelog: v0.37.0...v0.38.0

Features

• Add FT models supported and limits (eb83352)
• Add typing for completion responses related to logprobs (7be3686)
• Add wandb_entity argument to OpenAPI definition (71e55a9)
• Another try (d59291f)
• Change TrainingType default to null (cb4bdcb)
• update deployments schemas to include volume versions (1d3a34e)
• Update descriptions for endpoints (e7a8aaf)
• Update training type for price estimation too (52c3b77)

Bug Fixes

• client: avoid removing abort listener too early (1376258)
• client: preserve URL params already embedded in path (940974d)
• docs/contributing: correct pnpm link command (eab2b6e)
• fix request delays for retrying to be more respectful of high requested delays (11669ff)
• fixed autoscaling configs in deployments api (4dac51b)
• internal: skip tests that depend on mock server (be7e0e7)

Chores

• ci: skip uploading artifacts on stainless-internal branches (603c86c)
• configure new SDK language (b6f30b6)
• Fix various docstrings (af4c47f)
• internal/client: fix form-urlencoded requests (d73f69f)
• internal: avoid type checking errors with ts-reset (70ad44b)
• internal: move stringifyQuery implementation to internal function (54dc83f)
• internal: update dependencies to address dependabot vulnerabilities (e442dfd)
• Remove broken field LineCount from FileResponse (a0c187e)
• Revert adding mcp code. Code additions were unexpected. (bb39360)
• test: do not count install time for mock server timeout (4f232bf)
• Update descriptions for jig queue methods and properties (7fdfcca)
• update mock server docs (ac14bf7)
• update placeholder string (e481cda)

---

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

---

Note

Medium Risk
Touches core HTTP client behavior (URL/query building, retries, request body encoding, abort handling), which can subtly affect request semantics; remaining changes are mostly generated type/docs and CI/test maintenance.

Overview
Releases 0.38.0 with refreshed generated API surface: stronger/updated typings and docs across chat/completions (logprobs fields, prompt echo typing), fine-tuning (nullable training_type, wandb_entity), files (remove LineCount, tighten FileResponse), and beta deployments/clusters/jig (structured autoscaling configs, volume versioning, queue response schemas).

Client/runtime fixes include extracting stringifyQuery to internal/utils/query, preserving existing URL query params when building URLs, adding application/x-www-form-urlencoded body encoding support, adjusting retry delay behavior to better respect server-provided Retry-After, and avoiding premature abort-listener cleanup.

Build/test/ops updates: CI skips artifact upload on stl/* internal branches, scripts/mock gains deterministic startup timeout/logging, several mock-server-incompatible tests are skipped/adjusted, and deps are pinned via minimatch overrides/resolutions (lockfile updated).

^{Written by Cursor Bugbot for commit 54abcc5. This will update automatically on new commits. Configure here.}

[cursor]

Prompt interface defined in wrong namespace breaks ChatCompletion

High Severity

The ChatCompletion interface references ChatCompletion.Prompt at line 67, but the Prompt interface was placed inside the ChatCompletionAssistantMessageParam namespace instead of the ChatCompletion namespace. The ChatCompletion namespace only contains Choice and Warning. By contrast, Completion.Prompt in src/resources/completions.ts is correctly placed inside the Completion namespace. This is a code generation error that will prevent compilation.

Additional Locations (1)

• src/resources/chat/completions.ts#L66-L67

 

[cursor]

Retry delay accepts NaN and negative timeout values

Medium Severity

The retry timeout guard was changed from if (!(timeoutMillis && 0 <= timeoutMillis && timeoutMillis < 60 * 1000)) to if (timeoutMillis === undefined). The old condition also caught NaN, negative, and zero values, falling back to the default exponential backoff. The new condition only catches undefined, so if Date.parse(retryAfterHeader) - Date.now() produces NaN (invalid date) or a negative number (past date), sleep receives that value, bypassing backoff and causing immediate rapid retries.

 

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Free Tier Details

Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

[cursor]

Conditional prompt field incorrectly marked as required

Medium Severity

The prompt field on Completion was changed from optional (prompt?) to required (prompt), but the docstring states "When echo is true, the prompt is included in the response." Since this field is only populated when echo is enabled, marking it as required misleads TypeScript users into assuming it's always present — leading to potential runtime TypeError when accessing completion.prompt without echo: true.