| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
🧪 Testing To try out this version of the SDK: pip install 'https://pkg.stainless.com/s/kernel-python/b30c0e31182f09247bbf32823c256e27725fdbfc/kernel-0.88.0-py3-none-any.whl' Expires at: Fri, 11 Sep 2026 16:09:09 GMT |
Sorry, something went wrong.
The API spec gains region as a required field on browser responses (kernel/kernel#3270); strict response validation rejects the fixture without it. Safe against the current spec — models allow extra keys.
test: add region to the fake browser fixture
Stainless-Generated-From: f793e2f1d478198a0f75f553437b8b554b75368f
Stainless-Generated-From: 91d0b1968ff1d553bd8eb0700df9b6c8d9167bce
Stainless-Generated-From: d10c7305e30fe0869a9027e670f3b6ca1121870c
|
🤖 Release is at https://github.com/kernel/kernel-python-sdk/releases/tag/v0.89.0 🌻 |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Automated Release PR
0.89.0 (2026-08-12)
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
Large generated API surface (new required response fields like region) can break callers at runtime; CI changes alter the production release path and need correct merge behavior on the new next workflow.
Overview
Release 0.89.0 bundles OpenAPI-driven SDK updates with changes to how staging changes land in production and how releases are cut.
The client gains region (us-east / eu-west) on browser and pool create/list flows (immutable after create), typed network config with private_hosts on browsers and pools (create/update where supported), and expanded OrgLimits on GET /org/limits (managed auth connection caps, usage, and minimum health-check interval). Responses and params are wired through generated types, resources, tests, and docs; version bumps land in pyproject.toml, _version.py, and the changelog.
Release automation shifts to a next → main queue: staging promotion merges into production next (with conflict recovery PRs) instead of opening stainless/release promote PRs; release-please runs on next and main, builds a pinned Stainless release-please CLI, opens/updates the versioned PR from next, retires legacy promotion PRs/branches, and creates GitHub releases on main merges.
Reviewed by Cursor Bugbot for commit f202d64. Bugbot is set up for automated code reviews on this repo. Configure here.