Skip to content

release: 0.86.0 - #151

Open
stainless-app[bot] wants to merge 4 commits into
mainfrom
release-please--branches--main--changes--next--components--sdk
Open

release: 0.86.0#151
stainless-app[bot] wants to merge 4 commits into
mainfrom
release-please--branches--main--changes--next--components--sdk

Conversation

@stainless-app

@stainless-app stainless-app Bot commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

Automated Release PR

0.86.0 (2026-08-01)

Full Changelog: v0.85.0...v0.86.0

Features

  • Harden managed auth verification and login recovery (cc82869)
  • Report the unified concurrency ceiling from the org limits endpoint (791aaa8)

Bug Fixes

  • stlc: stop hand-edited CI workflows from blocking seals and builds (1662249)

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
Generated OpenAPI sync and documentation-only limit wording changes; the new auth field is additive and optional.

Overview
Release 0.86.0 bumps package/version metadata, changelog, and the pinned OpenAPI spec (.stats.yml).

Managed auth: Canonical Field types in auth connections (including SSE follow payloads) gain optional replace_existing, signaling when a submitted value must overwrite a stored credential after an explicit rejection.

Project limits: JSDoc for deprecated max_pooled_sessions no longer references a phased org rollout—docs now state it is always null on read and always rejected with 400 on write, reflecting fully unified browser concurrency under max_concurrent_sessions.

Reviewed by Cursor Bugbot for commit df2adb7. Bugbot is set up for automated code reviews on this repo. Configure here.

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.
@stainless-app

stainless-app Bot commented Jul 31, 2026

Copy link
Copy Markdown
Contributor Author

🧪 Testing

To try out this version of the SDK:

npm install 'https://pkg.stainless.com/s/kernel-typescript/cc8286943eff0537e3875d7bcc9bf9cd017f2656/dist.tar.gz'

Expires at: Mon, 31 Aug 2026 15:22:29 GMT
Updated at: Sat, 01 Aug 2026 15:22:29 GMT

@stainless-app
stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--sdk branch from b4e9755 to e6bee79 Compare July 31, 2026 18:07
@stainless-app stainless-app Bot changed the title release: 0.85.1 release: 0.86.0 Jul 31, 2026
@stainless-app
stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--sdk branch from e6bee79 to 544e20a Compare July 31, 2026 18:07
@stainless-app
stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--sdk branch from 544e20a to df2adb7 Compare August 1, 2026 15:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants