Repository navigation
release: 0.139.0 - #220
Open
kernel-internal[bot] wants to merge 4 commits into
Open
release: 0.139.0#220kernel-internal[bot] wants to merge 4 commits into
kernel-internal[bot] wants to merge 4 commits into
Conversation
…MCP invoke failures Stainless-Generated-From: 99d2df34644636e2590f1f9c6c3affcb165ed489
kernel-internal
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
November 3, 2026 15:02
e75f914 to
84a0c4e
Compare
Stainless-Generated-From: 3cdabb505d7b51988f5b58555d76d629f85fab8c
kernel-internal
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
November 3, 2026 17:10
84a0c4e to
1158b07
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.139.0 (2026-11-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
Medium Risk
Changes 1Password fill matching semantics and WebMCP invoke failure/retry expectations for integrators; the CLI workflow shift affects release automation timing and diff scope, not runtime SDK code paths in this diff.
Overview
Release 0.139.0 bumps version metadata and documents two API-facing behavior changes from the changelog.
1Password fill (
vaultitem.go): docs now say the 1Password extension decides whether an approved login matches the page (Kernel’s origin gate is gone).entry_idis described as needed when several entries are approved and the page origin does not identify exactly one—not when multiple entries merely share an origin.WebMCP invoke (
browserwebmcp.go): docs addtool_page_unloadedwhen the tool’s page is reloaded/replaced without the tool responding, alongsideoutcome_unknown. Both outcomes are not retried and setX-Should-Retry: falsebecause side effects may have occurred.InvokeRequestParam.Inputis documented as 4 MiB (was 1 MiB) after JSON serialization.The Update CLI Coverage workflow now runs on
release: publishedinstead of push to main, uses full git history and the published release tag for the SDK version, and bases the SDK diff onorigin/main’sgo.modso cumulative CLI update branches stay accurate. Agent instructions were tightened so coverage reports and diffs span everything since CLI main’s SDK version and the agent does not add CLI surface beyond what this SDK release exposes.Reviewed by Cursor Bugbot for commit 1158b07. Bugbot is set up for automated code reviews on this repo. Configure here.