release: 0.114.0 - #180
Merged
Merged
release: 0.114.0#180
Conversation
Stainless-Generated-From: 8f39036711533f5cf7d1dcae85d98c367dbf9d74
Stainless-Generated-From: 1ea489e4871d8446f69ea3f39d82ec4856d6491b
kernel-internal
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
September 28, 2026 17:04
a0a3312 to
8c2a06f
Compare
Stainless-Generated-From: 1995c3fd399a0dc1dbc1a88983b6bb0d0673d0f8
kernel-internal
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
September 28, 2026 17:24
8c2a06f to
40d94a1
Compare
Stainless-Generated-From: 6d937aebb18d99636c515de11d6958083e7ca24c
kernel-internal
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
September 29, 2026 20:21
40d94a1 to
4c2d926
Compare
Stainless-Generated-From: 8ac1635568224ca17c04e5c6f15ac6e66e31b932
rgarcia
previously approved these changes
Sep 30, 2026
rgarcia
left a comment
Contributor
There was a problem hiding this comment.
The generated 1Password input and response contracts look correct. Approving the SDK changes; publication still needs the deployment and end-to-end release gates cleared.
kernel-internal
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
September 30, 2026 13:34
4c2d926 to
f6e1c01
Compare
rgarcia
approved these changes
Sep 30, 2026
rgarcia
left a comment
Contributor
There was a problem hiding this comment.
Reviewed the regenerated release head, including the additional publishable-key model change and passing checks.
Contributor
Author
|
🤖 Release is at https://github.com/kernel/kernel-python-sdk/releases/tag/v0.114.0 🌻 |
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.114.0 (2026-09-30)
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
Large generated surface around vault credentials, 1Password fill/OAuth, and telemetry storage affects how integrators handle secrets and compliance-sensitive telemetry, though the SDK mostly mirrors API contracts.
Overview
Release 0.114.0 bumps the package and changelog and regenerates the client from the latest Kernel OpenAPI spec.
Browser telemetry gains an optional
telemetry.storageflag (withBrowserTelemetryStorageConfigon responses) across browser create/update, pools, acquire, and managed-auth connection flows—so callers can disable Kernel persistence when exporting via OTLP only.Managed auth responses now include
health_check_unavailable_reason(e.g.no_auth_check_url) and clearer docs thatstatusis last-known, not proof of a live session when verification fails.Vaults add 1Password-backed credentials: new
credential_accountitems, provider-discriminated credential specs/states (kernelvs1password), OAuth/approval actions, andperform_operationoverloads for1pw_*flows (access request, poll, fill, recover, token update). Link vault provider configs accept optionalpublishable_keyon create/update and expose it on read.Tests and
api.mdare updated to match the new request/response shapes.Reviewed by Cursor Bugbot for commit 1f0aabc. Bugbot is set up for automated code reviews on this repo. Configure here.