Skip to content

release: 0.91.0 - #162

Merged
stainless-app[bot] merged 4 commits into
mainfrom
release-please--branches--main--changes--next
Aug 14, 2026
Merged

release: 0.91.0#162
stainless-app[bot] merged 4 commits into
mainfrom
release-please--branches--main--changes--next

Conversation

@stainless-app

@stainless-app stainless-app Bot commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

Automated Release PR

0.91.0 (2026-08-14)

Features

  • Add customer-facing OTLP destination CRUD API (25f9b28)
  • Expose configurable browser memory (cb90eb7)
  • Require a name on credential providers and backfill unnamed rows (1f70e73)

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
Adds a new top-level client service and a new required JSON field on browser responses, which can affect consumers that assume a fixed response shape; OTLP destinations also involve endpoint URLs and redacted auth headers.

Overview
Release 0.91.0 bumps the package and docs from v0.90.0 to v0.91.0 and reflects five new configured API endpoints (139 total).

The client gains client.Telemetry with Destinations full CRUD for OTLP export targets (OtlpDestination, list pagination, id-or-name paths). Browser APIs add memory: optional BrowserMemoryRequest (8GiB / 16GiB) on create and a required BrowserMemory field on browser session responses (including pool acquire and invocation browser lists). Credential provider create/update param docs now state that names are trimmed and must be non-empty after trim.

Generated tests cover the new destination methods; browser tests include the new memory field.

Reviewed by Cursor Bugbot for commit 7cd93c2. Bugbot is set up for automated code reviews on this repo. Configure here.

Stainless-Generated-From: d8057f2928875212b8a37f02ab023978e471f4d5
@kernel-internal
kernel-internal Bot force-pushed the release-please--branches--main--changes--next branch from 0e588fa to 9a5f65a Compare August 13, 2026 20:52
@stainless-app

stainless-app Bot commented Aug 13, 2026

Copy link
Copy Markdown
Contributor Author

🧪 Testing

To try out this version of the SDK:

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

Expires at: Sun, 13 Sep 2026 18:12:10 GMT
Updated at: Fri, 14 Aug 2026 18:12:10 GMT

Stainless-Generated-From: e760ec2201481e0ea5b785b9def0aa474334eb9f
@stainless-app
stainless-app Bot force-pushed the release-please--branches--main--changes--next branch from 9a5f65a to cbc0971 Compare August 14, 2026 17:53
@kernel-internal
kernel-internal Bot force-pushed the release-please--branches--main--changes--next branch from cbc0971 to 18db92f Compare August 14, 2026 17:53
Stainless-Generated-From: 8e08b8b3680bc87c55f7d227162b7e3a9ae39dd2
@stainless-app
stainless-app Bot force-pushed the release-please--branches--main--changes--next branch from 18db92f to 2eaa1b9 Compare August 14, 2026 18:11
@kernel-internal
kernel-internal Bot force-pushed the release-please--branches--main--changes--next branch from 2eaa1b9 to 7cd93c2 Compare August 14, 2026 18:12

@cursor cursor Bot left a comment

Copy link
Copy Markdown

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 using high effort and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 7cd93c2. Configure here.

Comment thread telemetrydestination.go
// rotation path; sessions already exporting pick up the new values without
// restarting. Names and values must be valid HTTP header tokens, and the names and
// values together cannot exceed 8192 bytes.
Headers map[string]string `json:"headers,omitzero"`

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Update headers cannot encode deletions

Medium Severity

TelemetryDestinationUpdateParams.Headers is a map[string]string, so it cannot encode JSON null values. The field comment documents per-key merge where null deletes a header, which is the credential-rotation path for removing a stored header. Callers can only send string values, so a documented delete never reaches the API through the typed field.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 7cd93c2. Configure here.

@stainless-app
stainless-app Bot merged commit 9a6636d into main Aug 14, 2026
10 checks passed
@stainless-app

stainless-app Bot commented Aug 14, 2026

Copy link
Copy Markdown
Contributor Author

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