release: 0.64.0#122
Open
stainless-app[bot] wants to merge 3 commits into
Open
Conversation
|
Firetiger deploy monitoring skipped This PR didn't match the auto-monitor filter configured on your GitHub connection:
Reason: This is a release PR for kernel-node-sdk (a Node.js SDK), not a deployment to the kernel service itself; clarify which service this release affects or opt in manually for deploy monitoring. To monitor this PR anyway, reply with |
Contributor
Author
|
🧪 Testing To try out this version of the SDK: Expires at: Sun, 05 Jul 2026 21:37:46 GMT |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated Release PR
0.64.0 (2026-06-05)
Full Changelog: v0.63.0...v0.64.0
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
Telemetry config semantics changed from prior defaults (opt-in categories and monitor/screenshot gating), which can alter what events existing integrations receive without code changes.
Overview
Release 0.64.0 ships OpenAPI-driven updates to browser telemetry: opt-in category capture, an expanded event taxonomy, and refreshed docs on create/update params.
Telemetry categories are now opt-in—only categories explicitly set to
enabled: trueare captured; omitted categories are off. The default set whenenabled: truewithout per-category settings is documented as control, connection, system, and captcha, with CDP-heavy categories (console, network, page, interaction) and screenshot off unless opted in.BrowserTelemetryCategoriesConfiggains captcha, connection, control, screenshot, and system flags alongside the existing CDP categories.New typed SSE events include in-VM API calls (
api_call), captcha outcomes, CDP and live-view connect/disconnect, service crashes, and OOM kills. Collector-health monitor_* events move from categorysystemtomonitor(tied to CDP category capture); monitor_screenshot uses the opt-inscreenshotcategory instead of always-onsystembehavior described in older docs.Types and public exports are wired through
telemetry.ts,browsersbarrels, andapi.md; the browser create test now exercises all category flags. Version bumps coverpackage.json,src/version.ts, changelog, and release manifest.Reviewed by Cursor Bugbot for commit 04c59aa. Bugbot is set up for automated code reviews on this repo. Configure here.