release: 0.59.0#106
Open
stainless-app[bot] wants to merge 4 commits into
Open
Conversation
|
Firetiger deploy monitoring skipped This PR didn't match the auto-monitor filter configured on your GitHub connection:
Reason: This is an automated release PR for the Python SDK, not a code change affecting kernel API endpoints or Temporal workflows. To monitor this PR anyway, reply with |
Contributor
Author
|
🧪 Testing To try out this version of the SDK: Expires at: Sun, 28 Jun 2026 17:41:09 GMT |
a5b3f82 to
d8a8e5a
Compare
d8a8e5a to
74388de
Compare
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.59.0 (2026-05-29)
Full Changelog: v0.58.0...v0.59.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
Adding required
categoryon telemetry events and removing mobile proxy fields are breaking API/schema changes for SDK consumers and proxy clients.Overview
Release 0.59.0 bumps package version metadata and refreshes the pinned OpenAPI spec.
Browser telemetry event models now include a required
categoryfield (console,interaction,network,page, orsystem) on each event type, matching the API so clients can group or filter streams without inferring fromtypealone.Mobile proxy configuration in create/check/list/retrieve types is narrowed:
asn,carrier, andzipare removed fromConfigMobileProxyConfig(and the createTypedDict), leavingcountry,city, andstatewith updated docs for Byteful-style routing. Callers that still send the dropped fields will fail validation against the new schema.Reviewed by Cursor Bugbot for commit 74388de. Bugbot is set up for automated code reviews on this repo. Configure here.