release: 0.72.0

[stainless-app]

Automated Release PR

0.71.1 (2026-06-26)

Full Changelog: v0.71.0...v0.71.1

Bug Fixes

• api: browser pool profile omits save_changes (BrowserPoolProfile) (41f382e)

---

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
Patch release with generated OpenAPI/SDK type alignment for browser pools; no runtime client logic changes beyond typings and documentation.

Overview
Patch release 0.71.1 bumps the SDK version and refreshes the OpenAPI spec pointer; the functional change is in browser pool profile typing.

Pool create/update/config types no longer use Shared.BrowserProfile (which includes save_changes). They now use pool-specific Profile shapes with only id and name, matching the API contract that pooled browsers load profiles read-only and never persist changes. Docs on browserPools.create / update clarify that any save_changes sent at runtime is ignored, not rejected—so reusing a single-session profile object stays valid at the HTTP layer even though TypeScript no longer suggests save_changes for pools.

Generated tests drop save_changes from the optional create-params example.

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

[stainless-app]

🧪 Testing

To try out this version of the SDK:

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

Expires at: Sun, 26 Jul 2026 18:25:05 GMT
Updated at: Fri, 26 Jun 2026 18:25:05 GMT

[IlyaasK]

⚠️ This release ships a breaking change that's currently classified as a patch fix.

kernel/kernel#2484 changed the browser pool profile field: the type is now a pool-specific BrowserPoolProfile (id/name only) instead of the shared BrowserProfile, and save_changes is no longer part of the pool profile. The regen landed here as fix(api): browser pool profile omits save_changes, so release-please is cutting 0.71.1 (patch) with no BREAKING CHANGES section.

Per Sayan's review on #2484, this should be a minor bump (→ 0.72.0) with a flagged changelog entry:

• Breaking for typed SDK users: callers who imported/annotated the BrowserProfile type for a pool's profile, or read profile.save_changes off a pool create/update params object, must switch to the new BrowserPoolProfile type (no save_changes).
• Wire-compatible: inline object-literal callers and raw HTTP are unaffected.
• Behavior change: save_changes: true on a pool used to return 400 ("not supported for browser pools") and is now silently ignored.

Suggested fix so release-please reclassifies: re-mark the regen commit as fix!(api): … (or add a BREAKING CHANGE: footer) so it bumps minor and emits a BREAKING CHANGES section. Suggested entry:

⚠ BREAKING CHANGES

• api: browser pool profile is now BrowserPoolProfile (id/name only); save_changes is no longer accepted on pool profiles. Wire-compatible for inline object callers; typed callers using the pool profile type must update. save_changes on a pool is now silently ignored (was a 400).

[IlyaasK]

lgtm

[stainless-app]

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