Skip to content

release: 0.43.0#91

Merged
stainless-app[bot] merged 7 commits intomainfrom
release-please--branches--main--changes--next--components--sdk
Mar 10, 2026
Merged

release: 0.43.0#91
stainless-app[bot] merged 7 commits intomainfrom
release-please--branches--main--changes--next--components--sdk

Conversation

@stainless-app
Copy link
Contributor

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

Automated Release PR

0.43.0 (2026-03-10)

Full Changelog: v0.42.1...v0.43.0

Features

  • Add webdriver_ws_url and metro webdriver session proxy (cff6562)

Bug Fixes

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

Chores

  • ci: skip uploading artifacts on stainless-internal branches (2e40c24)
  • internal: codegen related update (1185eae)
  • internal: update dependencies to address dependabot vulnerabilities (51c1411)
  • update placeholder string (7608d8b)

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
Medium risk because it changes core HTTP client URL/query merging and retry backoff behavior, which can affect request correctness and rate-limit handling. Other changes are mostly release/version bumps and CI/dependency hygiene.

Overview
Bumps the SDK to 0.43.0 (manifest, package.json, lockfiles, src/version.ts, changelog) and updates the pinned OpenAPI spec metadata.

API surface: browser session-related responses now include webdriver_ws_url across browsers, browser pools, and invocation browser listings.

Client behavior: buildURL now preserves query params embedded in the provided path by merging url.searchParams with defaultQuery and per-request query, and retry handling now always honors server-provided retry-after/retry-after-ms delays instead of falling back when the delay is “too large.”

Ops/deps: CI artifact upload (OIDC + tarball) is skipped on stl/* branches, and minimatch is force-upgraded via overrides/resolutions (reflected in yarn.lock).

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

@stainless-app
Copy link
Contributor Author

stainless-app bot commented Mar 6, 2026

🧪 Testing

To try out this version of the SDK:

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

Expires at: Thu, 09 Apr 2026 16:07:02 GMT
Updated at: Tue, 10 Mar 2026 16:07:02 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.

Missing validation allows NaN/negative retry timeouts

Medium Severity

The old guard !(timeoutMillis && 0 <= timeoutMillis && timeoutMillis < 60 * 1000) validated that timeoutMillis was a positive, finite, reasonable number. The new check timeoutMillis === undefined only catches the undefined case. When Date.parse(retryAfterHeader) fails on an invalid date string, timeoutMillis becomes NaN (since NaN - Date.now() is NaN). Since NaN !== undefined, the fallback is skipped and sleep(NaN) is called, which resolves immediately via setTimeout(resolve, NaN). Similarly, a past-date retry-after header produces a negative timeoutMillis, also resolving immediately. Both cases bypass exponential backoff entirely, risking a retry storm against an already-struggling server.

Fix in Cursor Fix in Web

@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next--components--sdk branch from c4a7e8c to b883f9e Compare March 7, 2026 15:45
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next--components--sdk branch from b883f9e to 293d9e1 Compare March 7, 2026 15:46
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next--components--sdk branch from 293d9e1 to 21eb629 Compare March 7, 2026 15:50
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next--components--sdk branch from 21eb629 to c5c765f Compare March 10, 2026 02:30
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next--components--sdk branch from c5c765f to 084307b Compare March 10, 2026 16:06
@stainless-app stainless-app bot changed the title release: 0.42.2 release: 0.43.0 Mar 10, 2026
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next--components--sdk branch from 084307b to 8893279 Compare March 10, 2026 16:06
@stainless-app stainless-app bot merged commit f3704ee into main Mar 10, 2026
8 checks passed
@stainless-app
Copy link
Contributor Author

stainless-app bot commented Mar 10, 2026

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.

1 participant