release: 0.72.0

[stainless-app]

Automated Release PR

0.72.0 (2026-06-26)

Full Changelog: v0.71.0...v0.72.0

Bug Fixes

• api: browser pool profile omits save_changes (BrowserPoolProfile) (34423fb)

---

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
Narrow OpenAPI-driven type and doc alignment for browser pools; runtime API behavior is unchanged aside from clearer types and documentation.

Overview
Release 0.72.0 bumps package version metadata and refreshes the OpenAPI spec reference in .stats.yml.

The functional change is browser pool profile typing: create/update profile no longer uses shared BrowserProfile (which includes save_changes). Pool-specific Profile / BrowserPoolConfigProfile types only expose id and name, matching the API contract that pooled browsers load profiles read-only and never persist changes back.

browser_pools create/update docstrings now state that any save_changes sent on a pool profile is silently ignored (not rejected), so reusing a single-session profile dict remains valid at runtime. Tests drop save_changes from pool profile fixtures.

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

[stainless-app]

🧪 Testing

To try out this version of the SDK:

pip install 'https://pkg.stainless.com/s/kernel-python/34423fb99af7f43b7b9a6a023a4ec85902b1bcb2/kernel-0.71.0-py3-none-any.whl'

Expires at: Sun, 26 Jul 2026 18:24:55 GMT
Updated at: Fri, 26 Jun 2026 18:24:55 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 BrowserProfile/BrowserProfileParam 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 dict 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 dict callers; typed callers using the pool profile type must update. save_changes on a pool is now silently ignored (was a 400).

[stainless-app]

Release version edited manually

The Pull Request version has been manually set to 0.72.0 and will be used for the release.

If you instead want to use the version number 0.71.1 generated from conventional commits, just remove the label autorelease: custom version from this Pull Request.

[IlyaasK]

lgtm

[stainless-app]

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