Skip to content

release: 0.139.0 - #220

Open
kernel-internal[bot] wants to merge 4 commits into
mainfrom
release-please--branches--main--changes--next
Open

kernel-internal[bot] wants to merge 4 commits into
mainfrom
release-please--branches--main--changes--next

Conversation

@kernel-internal

@kernel-internal kernel-internal Bot commented Nov 2, 2026 •

Copy link
Copy Markdown
Contributor

Automated Release PR

0.139.0 (2026-11-03)

Features

  • Drop Kernel's origin gate from 1Password fill (34a9b40)
  • Pass through tool_page_unloaded and disable SDK retries for WebMCP invoke failures (a665adc)

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_id is 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 add tool_page_unloaded when the tool’s page is reloaded/replaced without the tool responding, alongside outcome_unknown. Both outcomes are not retried and set X-Should-Retry: false because side effects may have occurred. InvokeRequestParam.Input is documented as 4 MiB (was 1 MiB) after JSON serialization.

The Update CLI Coverage workflow now runs on release: published instead of push to main, uses full git history and the published release tag for the SDK version, and bases the SDK diff on origin/main’s go.mod so 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.

…MCP invoke failures

Stainless-Generated-From: 99d2df34644636e2590f1f9c6c3affcb165ed489
)

* Run the CLI updater on release and report on the whole evergreen PR

* Fetch full SDK history so the CLI updater can diff from older tags

---------

Co-authored-by: rgarcia <72655+rgarcia@users.noreply.github.com>
@kernel-internal
kernel-internal Bot force-pushed the release-please--branches--main--changes--next branch from e75f914 to 84a0c4e Compare November 3, 2026 15:02
Stainless-Generated-From: 3cdabb505d7b51988f5b58555d76d629f85fab8c
@kernel-internal
kernel-internal Bot force-pushed the release-please--branches--main--changes--next branch from 84a0c4e to 1158b07 Compare November 3, 2026 17:10
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.

1 participant