Skip to content

release: 0.16.0#31

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

release: 0.16.0#31
stainless-app[bot] wants to merge 6 commits intomainfrom
release-please--branches--main--changes--next

Conversation

@stainless-app
Copy link
Contributor

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

Automated Release PR

0.16.0 (2026-03-07)

Full Changelog: v0.15.0...v0.16.0

Features

  • Add strict metadata tags across mutable resources (8b5543e)
  • Snapshot (c4a0fbb)

Chores

  • ci: skip uploading artifacts on stainless-internal branches (0d9d654)
  • internal: codegen related update (e6a6702)
  • update placeholder string (bea84ac)

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
Introduces new snapshot endpoints and changes multiple List method signatures to require query params, which is a backwards-incompatible API surface change; also tweaks retry backoff behavior by always honoring Retry-After.

Overview
Adds snapshot support to the SDK: new top-level Snapshots service plus Instances.Snapshots for creating and restoring instance snapshots, and corresponding models/params.

Extends mutable resources (e.g., builds, images, devices, ingresses, volumes) with metadata tags and adds metadata-based filtering via new ...ListParams types; related List methods now take an explicit query param struct.

Updates CI to skip OIDC/artifact uploads on stl/* branches, adjusts retry delay handling to always respect Retry-After, and bumps the package/release docs to 0.16.0.

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

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

Expires at: Mon, 06 Apr 2026 19:53:35 GMT
Updated at: Sat, 07 Mar 2026 19:53:35 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.

Retry delay upper bound removed, risking indefinite blocking

Medium Severity

The retryDelay function previously capped the server's Retry-After value at one minute (retryAfterDelay < time.Minute), falling through to exponential backoff (max 8 seconds) for larger values. The new code removes this upper bound entirely via return max(0, retryAfterDelay), so a misconfigured or adversarial server returning a very large Retry-After (e.g. hours or days) will cause the client to block for that entire duration. The select on ctx.Done() at line 468 only helps if the caller set a context deadline — callers using context.Background() would hang indefinitely.

Fix in Cursor Fix in Web

@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from ee5a272 to 7bda7cf Compare March 7, 2026 18:34
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 7bda7cf to 1fcdb42 Compare March 7, 2026 19:52
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 1fcdb42 to ffaf115 Compare March 7, 2026 19:53
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