release: 0.91.0 - #162
Conversation
Stainless-Generated-From: d8057f2928875212b8a37f02ab023978e471f4d5
0e588fa to
9a5f65a
Compare
|
🧪 Testing To try out this version of the SDK: Expires at: Sun, 13 Sep 2026 18:12:10 GMT |
Stainless-Generated-From: e760ec2201481e0ea5b785b9def0aa474334eb9f
9a5f65a to
cbc0971
Compare
cbc0971 to
18db92f
Compare
Stainless-Generated-From: 8e08b8b3680bc87c55f7d227162b7e3a9ae39dd2
18db92f to
2eaa1b9
Compare
2eaa1b9 to
7cd93c2
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.
❌ 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.
| // 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"` |
There was a problem hiding this comment.
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.
Reviewed by Cursor Bugbot for commit 7cd93c2. Configure here.
|
🤖 Release is at https://github.com/kernel/kernel-go-sdk/releases/tag/v0.91.0 🌻 |


Automated Release PR
0.91.0 (2026-08-14)
Features
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.0tov0.91.0and reflects five new configured API endpoints (139 total).The client gains
client.TelemetrywithDestinationsfull CRUD for OTLP export targets (OtlpDestination, list pagination, id-or-name paths). Browser APIs addmemory: optionalBrowserMemoryRequest(8GiB/16GiB) on create and a requiredBrowserMemoryfield 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.