Skip to content

release: 0.57.1#264

Open
stainless-app[bot] wants to merge 8 commits intomainfrom
release-please--branches--main--changes--next--components--sdk
Open

release: 0.57.1#264
stainless-app[bot] wants to merge 8 commits intomainfrom
release-please--branches--main--changes--next--components--sdk

Conversation

@stainless-app
Copy link
Contributor

@stainless-app stainless-app bot commented Mar 7, 2026

Automated Release PR

0.57.1 (2026-03-12)

Full Changelog: v0.57.0...v0.57.1

Bug Fixes

  • client: preserve URL params already embedded in path (d239b56)

Chores

  • ci: skip uploading artifacts on stainless-internal branches (ce5a368)
  • internal: codegen related update (f0d0298)
  • internal: update dependencies to address dependabot vulnerabilities (cb6bfc8)
  • test: do not count install time for mock server timeout (9ae9dad)
  • update placeholder string (44a82b1)

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
Modifies core request URL construction and retry backoff behavior, which can affect all API calls if query merging or retry timing changes are incorrect. Remaining changes are largely CI/test/package maintenance and dependency pinning.

Overview
Bumps the SDK to 0.57.1 and updates release metadata (CHANGELOG.md, manifest, OpenAPI stats).

Fixes the client’s URL building to preserve query parameters already present in the request path by merging url.searchParams with defaultQuery and per-request query params in src/client.ts.

CI/test reliability updates: artifact upload in ci.yml now skips stl/* branches, scripts/mock pre-installs Prism and adds a 30s startup timeout with better logging, and file upload tests use simpler placeholder content. Also pins minimatch via overrides/resolutions and updates yarn.lock accordingly.

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

@stainless-app
Copy link
Contributor Author

stainless-app bot commented Mar 7, 2026

🧪 Testing

To try out this version of the SDK:

npm install 'https://pkg.stainless.com/s/mixedbread-typescript/359413cc420ff27faab32239fd18e65abfe2b6bb/dist.tar.gz'

Expires at: Sat, 11 Apr 2026 08:17:51 GMT
Updated at: Thu, 12 Mar 2026 08:17:51 GMT

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.

if (!(timeoutMillis && 0 <= timeoutMillis && timeoutMillis < 60 * 1000)) {
// If the API asks us to wait a certain amount of time, just do what it
// says, but otherwise calculate a default
if (timeoutMillis === undefined) {
Copy link

Choose a reason for hiding this comment

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

Malformed retry-after header bypasses backoff due to NaN

Medium Severity

When the retry-after header contains a string that is neither a valid number nor a valid date (e.g., a malformed value), Date.parse() returns NaN, making timeoutMillis equal to NaN. The new guard timeoutMillis === undefined evaluates to false for NaN, so the default backoff is never applied and sleep(NaN) resolves immediately (since setTimeout treats NaN as 0). The old guard caught this because NaN is falsy. This could cause aggressive retry storms against a server sending malformed headers.

Additional Locations (1)

Fix in Cursor Fix in Web

@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next--components--sdk branch from e615bb8 to 2ded8ea Compare March 7, 2026 05:38
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next--components--sdk branch 2 times, most recently from 3840cc5 to f34a21c Compare March 8, 2026 00:15
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next--components--sdk branch from f34a21c to a85abe5 Compare March 10, 2026 08:33
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next--components--sdk branch from a85abe5 to 9663dfe Compare March 12, 2026 08:17
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