release: 0.86.0 - #151
Open
stainless-app[bot] wants to merge 3 commits into
Open
Conversation
Editing the generated CI/release workflows in an SDK repo is supported: stlc writes them once and then leaves them under the repo's ownership. Two safety checks did not account for that and could refuse to seal custom code, or refuse to build, over workflow edits that were never at risk of being overwritten. The seal refusal could not be cleared by rebuilding. Sealing is also now recorded in place rather than under a new filename each time, so an interrupted build can no longer leave a workspace with no record of its sealed custom code, and sealing one branch no longer discards the record for another.
Contributor
Author
|
🧪 Testing To try out this version of the SDK: Expires at: Sun, 30 Aug 2026 18:07:54 GMT |
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next--components--sdk
branch
from
July 31, 2026 18:07
b4e9755 to
e6bee79
Compare
stainless-app
Bot
force-pushed
the
release-please--branches--main--changes--next--components--sdk
branch
from
July 31, 2026 18:07
e6bee79 to
544e20a
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.86.0 (2026-07-31)
Full Changelog: v0.85.0...v0.86.0
Features
Bug Fixes
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
Mostly version and doc-only changes; limit semantics are clarified, not new runtime logic in this diff.
Overview
Release 0.86.0 bumps package and manifest versions and refreshes the pinned OpenAPI spec (
.stats.yml).The only behavioral/SDK surface change in the diff is documentation on project limits: deprecated
max_pooled_sessionsis described as always null on read and always rejected with 400 on write, without the previous “once unified concurrency is enabled for your organization” caveat.max_concurrent_sessionsremains the unified browser concurrency field.Changelog also notes reporting the org limits unified concurrency ceiling and an STLC CI workflow fix; those are not reflected in the TypeScript diff beyond the spec pin and version bump.
yarn.lockpicks up a patch bump forbrace-expansion.Reviewed by Cursor Bugbot for commit 544e20a. Bugbot is set up for automated code reviews on this repo. Configure here.