Repository navigation
release: 0.153.0 - #224
Merged
masnwilliams merged 2 commits intoNov 20, 2026
Merged
release: 0.153.0#224
Conversation
Stainless-Generated-From: e609f7869b7b3a630d90e745be47feaff98d261d
masnwilliams
approved these changes
Nov 20, 2026
Contributor
Author
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.153.0 (2026-11-20)
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
Low Risk
Additive OpenAPI/SDK types and optional response fields; no client breaking changes unless callers assumed
costwas absent.Overview
Release 0.153.0 adds typed support for provisional browser-session cost on browser detail-style responses.
A new
BrowserCostmodel (kernel.types.BrowserCost) describes billing state:status(provisional,pending, orunavailable), optionalas_of, and optionalestimated_usage_spend_usd(gross meter spend, not an invoice total). It is exported from the public types package and documented inapi.md.Browser session response types (
BrowserCreateResponse,BrowserRetrieveResponse,BrowserUpdateResponse,BrowserListResponse,BrowserPoolAcquireResponse,InvocationListBrowsersResponse, etc.) now include an optionalcostfield. Docstrings state this is intended for GET detail responses and is omitted from list and other browser responses when the API does not return it.Version metadata is bumped to 0.153.0 (
pyproject.toml,_version.py, release manifest, changelog).Reviewed by Cursor Bugbot for commit 996a268. Bugbot is set up for automated code reviews on this repo. Configure here.