release: 0.93.0 - #171
Open
stainless-app[bot] wants to merge 2 commits into
Open
Conversation
Stainless-Generated-From: fdf3fb3ccd349dd4841bc00b708c7d0b2bcaca41
kernel-internal
Bot
force-pushed
the
release-please--branches--main--changes--next--components--sdk
branch
from
August 18, 2026 21:09
ae5315c to
819d310
Compare
Contributor
Author
|
🧪 Testing To try out this version of the SDK: Expires at: Thu, 17 Sep 2026 21:09:37 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.93.0 (2026-08-18)
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
Required new
reasonon canonical authFieldtypes and removal ofreplace_existingcan break TypeScript clients and change login UX logic in managed-auth flows.Overview
Release 0.93.0 bumps
@onkernel/sdkand documents hardened canonical managed auth field metadata from the API.Canonical
Fieldobjects on managed auth connections (and SSEmanaged_auth_stateevents) now require areasonof'missing'or'rejected', so clients can tell whether input is needed because nothing was stored or because a prior value was rejected (e.g. wrong password). The optionalreplace_existingflag was removed from those types; that behavior is expressed throughreason: 'rejected'instead.Integrators building against
fields/field_valuesshould readreasonwhen rendering prompts or deciding how to resubmit credentials.Reviewed by Cursor Bugbot for commit 819d310. Bugbot is set up for automated code reviews on this repo. Configure here.