Skip to content

release: 0.149.0 - #240

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

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

Conversation

@kernel-internal

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

Copy link
Copy Markdown
Contributor

Automated Release PR

0.149.0 (2026-11-16)

Features

  • Add reports API and report type discovery (73a9a6b)
  • Add tasks API: create, list, get, and link browsers (67da753)
  • Let vault item events be read after the item or vault is deleted (908bc54)

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
Mostly additive, Stainless-generated API client surface plus docs and CI pins; vault changes are type/description only, not runtime auth logic in this repo.

Overview
Release 0.149.0 adds generated client support for tasks, reports, and report type discovery, and extends vault item/event typings and CI glue.

The Kernel client now exposes tasks (create, get, list, link browsers), reports (schema-validated create/get/list against a task), and reportTypes (list/retrieve types and per-version JSON Schema via reportTypes.versions.retrieve). Matching resource modules, api.md, exports, and skipped API resource tests are included; endpoint count in .stats.yml rises 179 → 189.

Vault items documentation and types change for checkout authorization fields (amount_authority values, charge-related optional fields) and item events gain optional include_deleted for reading events after item/vault deletion.

Automation adds a machine-generated GitHub Actions lockfile, bumps the pinned pnpm/action-setup in release-please, and tightens MCP coverage workflow behavior (richer rebase conflict errors, SDK audit baseline when the update branch is regenerated). The MCP updater prompt gains guidance on where tool copy lives and destructiveHint rules.

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

masnwilliams and others added 8 commits November 12, 2026 20:50
Stainless-Generated-From: ff07542209cb21ce43563832867d637031305c63
Keep tool descriptions to choosing an action, put input rules on
parameters and post-call guidance in responses, respect the description
size guard, and set destructiveHint from the tool's actions.
Tell the MCP coverage updater where description text goes
Co-authored-by: rgarcia <72655+rgarcia@users.noreply.github.com>
Stainless-Generated-From: 368f79bc628ef39f4c4973db3fcb7ebb3c4c1b97

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 368e6eb. Configure here.

# main's SDK version, not only the ones since the last run.
old_version=$(git show origin/main:package.json | jq -er '.dependencies["@onkernel/sdk"]')
# the baseline's SDK version, not only the ones since the last run.
old_version=$(git show "$baseline_ref:package.json" | jq -er '.dependencies["@onkernel/sdk"]')

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Prompt ignores regenerated SDK baseline

Medium Severity

After a bot-only regenerate, SDK and OpenAPI diffs are built from the merge-base SDK version, but the agent prompt still says those diffs start at $MAIN_SHA and that earlier runs may already have covered them on this branch. That branch was reset to main, so the extra hunks are the dropped coverage this change is meant to restore, and the agent can skip them.

Additional Locations (2)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 368e6eb. Configure here.

Stainless-Generated-From: 7416198bc84673817c339be748d49936e6369e30
@kernel-internal
kernel-internal Bot force-pushed the release-please--branches--main--changes--next--components--sdk branch from 368e6eb to 57f906d Compare November 16, 2026 22:29
Stainless-Generated-From: e77cbb586c0807968f04f179f0848b60456e7929
@kernel-internal
kernel-internal Bot force-pushed the release-please--branches--main--changes--next--components--sdk branch from 57f906d to 7d81c82 Compare November 16, 2026 23: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.

2 participants