release: 0.99.0 - #166
Open
stainless-app[bot] wants to merge 2 commits into
Open
Conversation
Stainless-Generated-From: ae612ef5de5a9136bfc5f8cac5c6990b9d82e233
kernel-internal
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
September 3, 2026 14:28
608878d to
6937e0a
Compare
Contributor
Author
|
🧪 Testing To try out this version of the SDK: Expires at: Sat, 03 Oct 2026 14:28:42 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.99.0 (2026-09-03)
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 response fields on a generated Pydantic model with no client or auth changes; typical semver minor API surface expansion.
Overview
Release 0.99.0 bumps package version metadata (
pyproject.toml,_version.py, release manifest) and documents the release inCHANGELOG.md.The functional SDK change extends
OtlpDestinationwith OTLP delivery health fields returned from destination APIs: requiredconsecutive_failures(current failure streak;0means last outcome succeeded) and optionallast_export_at,last_error_at, and sanitizedlast_error. Docstrings note that error fields can remain set after a later success, so callers should useconsecutive_failuresfor live health.Reviewed by Cursor Bugbot for commit 6937e0a. Bugbot is set up for automated code reviews on this repo. Configure here.