release: 0.79.0#142
Open
stainless-app[bot] wants to merge 2 commits into
Open
Conversation
Contributor
Author
|
🧪 Testing To try out this version of the SDK: Expires at: Fri, 14 Aug 2026 20:55:38 GMT |
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.79.0 (2026-07-15)
Full Changelog: v0.78.1...v0.79.0
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
New optional telemetry fields on pool lifecycle APIs affect data capture and compliance-sensitive behavior; enforcement lives server-side, but callers can now enable broader capture from pools and per-acquire overrides.
Overview
Release 0.79.0 bumps package/version metadata and points
.stats.ymlat a new OpenAPI spec snapshot.The functional SDK change is telemetry on browser pools: pool config responses can include active
telemetry; create and update accept optionaltelemetry(enabledplus per-categorybrowserflags, reusing existing browser telemetry types); acquire accepts a lease-scopedtelemetryoverride that merges like browser PATCH and resets on release with reuse. Generated tests includetelemetryin the optional create params example.Changelog calls out pool telemetry with BAA enforcement on the API side; this PR does not add BAA-specific types beyond the regenerated contract.
Reviewed by Cursor Bugbot for commit 906c5d7. Bugbot is set up for automated code reviews on this repo. Configure here.