release: 0.70.0

[stainless-app]

Automated Release PR

0.70.0 (2026-06-24)

Full Changelog: v0.69.0...v0.70.0

Features

• Add GET /browsers/{id}/telemetry/events (read from S2) (2c3e61e)
• Align browser-pool timeout/viewport/fill-rate contract with implementation; reject save_changes on update (a986c45)
• api: support per-acquire start_url override on browser pool acquire (1c675a3)
• api: add GET /extensions/{id_or_name}/metadata (373f33b)
• api: resolve GET /org/projects/{id} by ID or name (395e0a7)
• Forward replay param through telemetry stream passthrough (ae02eeb)

Bug Fixes

• don't misroute telemetry/events to the browser VM (95487e0)

---

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

Low Risk
Mostly additive, OpenAPI-generated client surface with doc alignment; the telemetry events routing fix is server-side, while SDK changes are backward compatible aside from new optional params.

Overview
Release v0.70.0 bumps the package and docs from 0.69.0 and reflects a newer OpenAPI spec (122 endpoints).

Browser telemetry gains Events / EventsAutoPaging for GET /browsers/{id}/telemetry/events, with time-window, category, limit, and offset query params and BrowserTelemetryEventsResponse envelopes. The SSE StreamStreaming path now sends BrowserTelemetryStreamParams (including new replay) on the request and documents replay-from-buffer behavior; Last-Event-ID handling is unchanged.

Extensions add Get → GET /extensions/{id_or_name}/metadata and ExtensionGetResponse without downloading the ZIP.

Browser pools add optional per-acquire start_url on BrowserPoolAcquireParams. Pool create/update field comments now spell out timeout bounds (10–259200s) and fill_rate lower-bound enforcement; shared viewport param docs accept arbitrary positive dimensions.

Projects Get is documented to resolve by ID or name (same path parameter).

Version pins in README, CHANGELOG, api.md, and internal/version.go are updated; tests cover the new telemetry events and extension get calls.

^{Reviewed by Cursor Bugbot for commit 736c0c7. Bugbot is set up for automated code reviews on this repo. Configure here.}

[firetiger-agent]

Firetiger deploy monitoring skipped

This PR didn't match the auto-monitor filter configured on your GitHub connection:

PRs in the kernel, infra, hypeman, and hypeship repos. kernel is a ~mono repo with many logical services underneath, ensure to focus on the implicated service for the PR

Reason: This is a release PR for kernel-go-sdk (a Go SDK), not a PR in the kernel, infra, hypeman, or hypeship repositories themselves.

To monitor this PR anyway, reply with @firetiger monitor this.

[stainless-app]

🧪 Testing

To try out this version of the SDK:

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

Expires at: Fri, 24 Jul 2026 17:48:32 GMT
Updated at: Wed, 24 Jun 2026 17:48:32 GMT

[cursor]

Update test sends rejected save_changes

Medium Severity

Release 0.70.0 documents that browser pool update rejects profile.save_changes, but TestBrowserPoolUpdateWithOptionalParams still sets SaveChanges: kernel.Bool(true) on BrowserPoolUpdateParams.Profile. The same commit adjusts TimeoutSeconds for the new minimum without fixing this payload, so integration runs against a 0.70.0 API are likely to fail while the test still expects success.

 

^{Reviewed by Cursor Bugbot for commit 7fa3690. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

There are 2 total unresolved issues (including 1 from previous review).

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

^{Reviewed by Cursor Bugbot for commit 9c6c44c. Configure here.}

[cursor]

Telemetry events VM routing conflict

High Severity

The new Events method, which fetches historical telemetry, is misrouted. When a browser session is cached, the client's middleware sends all browsers/{id}/telemetry/* requests to the browser VM. Since the events endpoint should query historical data from the control plane, this routing causes the call to fail or return incorrect data.

 

^{Reviewed by Cursor Bugbot for commit 9c6c44c. Configure here.}

[stainless-app]

🤖 Release is at https://github.com/kernel/kernel-go-sdk/releases/tag/v0.70.0 🌻