Skip to content

release: 0.70.0#130

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

release: 0.70.0#130
stainless-app[bot] wants to merge 3 commits into
mainfrom
release-please--branches--main--changes--next--components--sdk

Conversation

@stainless-app

@stainless-app stainless-app Bot commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

Automated Release PR

0.70.0 (2026-06-22)

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

Features

  • Align browser-pool timeout/viewport/fill-rate contract with implementation; reject save_changes on update (c3fe382)

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
Documentation and release metadata only; no runtime client logic changes in the diff.

Overview
Release 0.70.0 bumps package metadata (package.json, src/version.ts, release-please manifest) and points Stainless at a new OpenAPI spec snapshot in .stats.yml.

Generated browser pool JSDoc now documents fill_rate_per_minute (default 10, typical org cap 25 with per-org overrides) and timeout_seconds bounds (10–259200, default 600) on create/update/config types in browser-pools.ts. BrowserViewport field docs in shared.ts state that width, height, and optional refresh rate accept any positive integer.

The browser-pools create test example uses timeout_seconds: 10 instead of 60 to match the documented minimum.

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

@firetiger-agent

Copy link
Copy Markdown

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 an automated release PR for the kernel-node-sdk repository, which appears to be a Node.js SDK client library rather than a service requiring deploy monitoring.

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

@stainless-app

stainless-app Bot commented Jun 22, 2026

Copy link
Copy Markdown
Contributor Author

🧪 Testing

To try out this version of the SDK:

npm install 'https://pkg.stainless.com/s/kernel-typescript/c3fe38247a404a040812508e21c1252c9c421279/dist.tar.gz'

Expires at: Wed, 22 Jul 2026 17:42:30 GMT
Updated at: Mon, 22 Jun 2026 17:42:30 GMT

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