Skip to content

release: 0.38.0#212

Open
stainless-app[bot] wants to merge 23 commits intomainfrom
release-please--branches--main--changes--next--components--together-ai
Open

release: 0.38.0#212
stainless-app[bot] wants to merge 23 commits intomainfrom
release-please--branches--main--changes--next--components--together-ai

Conversation

@stainless-app
Copy link
Contributor

@stainless-app stainless-app bot commented Feb 5, 2026

Automated Release PR

0.38.0 (2026-03-02)

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

Features

  • update deployments schemas to include volume versions (1d3a34e)
  • Update descriptions for endpoints (e7a8aaf)

Bug Fixes

  • client: avoid removing abort listener too early (1376258)
  • docs/contributing: correct pnpm link command (eab2b6e)
  • internal: skip tests that depend on mock server (be7e0e7)

Chores

  • 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)
  • Remove broken field LineCount from FileResponse (a0c187e)
  • Revert adding mcp code. Code additions were unexpected. (bb39360)
  • Update descriptions for jig queue methods and properties (7fdfcca)
  • update mock server docs (ac14bf7)

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
Updates request/encoding behavior in the core client (abort handling and application/x-www-form-urlencoded bodies) and tightens/extends several public types (notably Jig volume versioning), which could affect runtime behavior and downstream TypeScript users.

Overview
Bumps the package to v0.38.0 (manifest, package.json, src/version.ts, changelog) and refreshes the generated spec metadata.

Client behavior changes: moves stringifyQuery into a new internal util (src/internal/utils/query.ts), adds application/x-www-form-urlencoded body encoding support using that helper, and fixes abort handling by no longer removing the abort listener too early.

API/schema updates: extends Jig deployment volume mounts with an optional version, adds volume versioning fields (current_version, version_history, mounted_by) to Jig volumes, loosens clusters region from a fixed union to string and updates region listing shape, and tightens various response object fields to string literals while removing the unused/broken FileResponse.LineCount and the exported FileObject type. Tests/docs are adjusted accordingly (skip mock-incompatible tests and update mock/pnpm instructions).

Written by Cursor Bugbot for commit 19b3c28. This will update automatically on new commits. Configure here.

@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next--components--together-ai branch from 8bd7915 to e8ded67 Compare February 6, 2026 18:33
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next--components--together-ai branch from e8ded67 to 98fe444 Compare February 6, 2026 20:54
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next--components--together-ai branch from 98fe444 to b62d5d4 Compare February 10, 2026 23:25
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next--components--together-ai branch from b62d5d4 to 14ff965 Compare February 11, 2026 14:05
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next--components--together-ai branch from 14ff965 to ef22972 Compare February 12, 2026 19:14
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next--components--together-ai branch from ef22972 to 67b2c1e Compare February 12, 2026 20:16
@stainless-app stainless-app bot changed the title release: 0.37.1 release: 0.38.0 Feb 12, 2026
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next--components--together-ai branch from 67b2c1e to dde6e53 Compare February 12, 2026 20:16
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next--components--together-ai branch from dde6e53 to e9717d6 Compare February 17, 2026 13:07
return await this.fetch.call(undefined, url, fetchOptions);
} finally {
clearTimeout(timeout);
if (signal) signal.removeEventListener('abort', abort);
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Abort listeners accumulate across completed requests

Medium Severity

fetchWithTimeout no longer removes the abort listener from the caller-provided signal after fetch completes. Reusing one AbortSignal for many requests now retains one closure per request, causing unbounded listener growth and extra abort callbacks long after requests have finished.

Fix in Cursor Fix in Web

@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next--components--together-ai branch from e9717d6 to f891d52 Compare February 17, 2026 17:35
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next--components--together-ai branch from f891d52 to c706e22 Compare February 18, 2026 17:46
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next--components--together-ai branch from c706e22 to cda41d6 Compare February 19, 2026 03:08
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next--components--together-ai branch from cda41d6 to 8920203 Compare February 19, 2026 15:11
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next--components--together-ai branch from 8920203 to cf91872 Compare February 19, 2026 16:32
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next--components--together-ai branch from cf91872 to 454744e Compare February 21, 2026 22:05
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next--components--together-ai branch from 454744e to 32cecaa Compare February 23, 2026 16:37
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next--components--together-ai branch from 32cecaa to ea937ec Compare February 23, 2026 19:20
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

return {
bodyHeaders: { 'content-type': 'application/x-www-form-urlencoded' },
body: this.stringifyQuery(body as Record<string, unknown>),
};
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Form encoding depends on exact content-type

Low Severity

buildBody() only switches to form-urlencoding when headers.values.get('content-type') equals exactly application/x-www-form-urlencoded. If callers set a valid variant like application/x-www-form-urlencoded; charset=utf-8, the body falls through to #encoder, likely producing a different encoding than the header implies.

Fix in Cursor Fix in Web

@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next--components--together-ai branch from ea937ec to 2bc10b5 Compare February 26, 2026 16:04
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next--components--together-ai branch from 2bc10b5 to 19b3c28 Compare March 2, 2026 14:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants