Skip to content

release: 0.57.0#106

Open
stainless-app[bot] wants to merge 7 commits into
mainfrom
release-please--branches--main--changes--next
Open

release: 0.57.0#106
stainless-app[bot] wants to merge 7 commits into
mainfrom
release-please--branches--main--changes--next

Conversation

@stainless-app
Copy link
Copy Markdown
Contributor

@stainless-app stainless-app Bot commented May 19, 2026

Automated Release PR

0.57.0 (2026-05-22)

Full Changelog: v0.56.0...v0.57.0

Features

  • [kernel-1116] browser events api integration (e0a367b)
  • api: type can_reauth_reason as an enum on ManagedAuth (61f5842)
  • browsers: accept chrome_policy on POST /browsers (KERNEL-1216) (6f29adc)
  • EOL persistent browsers: openapi limits (b79f2fd)

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
Moderate risk due to a large generated surface-area update (new telemetry SSE service/types) plus API type changes/removals that may break existing consumers (persistent browser fields, can_reauth_reason typing).

Overview
Bumps the SDK to v0.57.0 and updates generated API bindings.

Adds browser telemetry/event streaming via a new Browsers.Telemetry.Stream SSE endpoint, including telemetry config params on browser create/update and extensive new event/union types/constants.

Updates browser session models to accept/echo chrome_policy, removes deprecated persistent browser support (delete-by-persistent-id, persistence types, and project persistent-session limits), and types ManagedAuth.can_reauth_reason as a dedicated enum. Also hardens the SSE decoder to skip comment-only keepalive frames (with new tests).

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

@stainless-app
Copy link
Copy Markdown
Contributor Author

stainless-app Bot commented May 19, 2026

🧪 Testing

To try out this version of the SDK:

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

Expires at: Sun, 21 Jun 2026 16:49:10 GMT
Updated at: Fri, 22 May 2026 16:49:10 GMT

@firetiger-agent
Copy link
Copy Markdown

Firetiger deploy monitoring skipped

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

Any PR that changes the kernel API. Monitor changes to API endpoints (packages/api/cmd/api/) and Temporal workflows (packages/api/lib/temporal) in the kernel repo

Reason: This is an automated release PR for the SDK package, not a change to kernel API endpoints or Temporal workflows in packages/api/cmd/api/ or packages/api/lib/temporal.

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

@stainless-app stainless-app Bot force-pushed the release-please--branches--main--changes--next branch from 7fb7163 to d291579 Compare May 21, 2026 18:53
@stainless-app stainless-app Bot force-pushed the release-please--branches--main--changes--next branch from d291579 to ad1a550 Compare May 22, 2026 16:38
Copy link
Copy Markdown

@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.

Fix All in Cursor

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

Reviewed by Cursor Bugbot for commit ad1a550. Configure here.

Comment thread browsertelemetry.go
@stainless-app stainless-app Bot force-pushed the release-please--branches--main--changes--next branch from ad1a550 to 9b51c99 Compare May 22, 2026 16:49
@stainless-app stainless-app Bot force-pushed the release-please--branches--main--changes--next branch from 9b51c99 to d5b3657 Compare May 22, 2026 19:17
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