Skip to content

release: 0.42.2#87

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

release: 0.42.2#87
stainless-app[bot] wants to merge 4 commits intomainfrom
release-please--branches--main--changes--next

Conversation

@stainless-app
Copy link
Contributor

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

Automated Release PR

0.42.2 (2026-03-07)

Full Changelog: v0.42.1...v0.42.2

Chores

  • ci: skip uploading artifacts on stainless-internal branches (0586ec1)
  • internal: codegen related update (63ecb44)
  • update placeholder string (82510c4)

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
Changes retry backoff behavior by always honoring Retry-After/Retry-After-Ms (clamped to non-negative), which can materially affect request timing and throughput under error conditions. Other updates are CI gating and routine release/version bumps.

Overview
Releases v0.42.2. Updates version metadata (internal/version.go, .release-please-manifest.json), documentation (README.md), and CHANGELOG.md.

CI artifact uploads are now skipped on internal stl/* branches. The build job only fetches an OIDC token and uploads the tarball when the ref does not start with refs/heads/stl/.

Retry behavior change: internal/requestconfig.retryDelay now always uses the server-provided retry delay (via Retry-After headers) and clamps negative values to 0, instead of ignoring large values.

Test fixtures update placeholder upload content strings from "some file contents" to "Example data".

Written by Cursor Bugbot for commit 28c58ac. 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:

Download and unzip: 'https://pkg.stainless.com/s/kernel-go/82510c497a99e3a671b695667cc59aa66b8605ac/source.zip'. Run 'go mod edit -replace github.com/kernel/kernel-go-sdk=/path/to/unzipped_directory'.

Expires at: Mon, 06 Apr 2026 15:46:51 GMT
Updated at: Sat, 07 Mar 2026 15:46: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 the API asks us to wait a certain amount of time (and it's a reasonable amount),
// just do what it says.

if retryAfterDelay, ok := parseRetryAfterHeader(res); ok && 0 <= retryAfterDelay && retryAfterDelay < time.Minute {
Copy link

Choose a reason for hiding this comment

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

Removed upper bound allows unbounded retry delay

Medium Severity

The retryDelay function previously capped server-provided Retry-After values at under one minute, falling through to exponential backoff (max 8 seconds) for larger values. The new code removes that upper bound entirely, meaning a server sending a large Retry-After value (e.g., hours or days) will cause the client to block for that entire duration. While ctx.Done() in the select provides protection when a context deadline is set, callers without a deadline could experience unbounded blocking.

Fix in Cursor Fix in Web

@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 7338e85 to ee5e3db Compare March 7, 2026 15:44
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from ee5e3db to 28c58ac Compare March 7, 2026 15:46
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