Repository navigation
release: 0.149.0 - #240
release: 0.149.0#240kernel-internal[bot] wants to merge 11 commits into
Conversation
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
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ 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"]') |
There was a problem hiding this comment.
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)
Reviewed by Cursor Bugbot for commit 368e6eb. Configure here.
Stainless-Generated-From: 7416198bc84673817c339be748d49936e6369e30
368e6eb to
57f906d
Compare
Stainless-Generated-From: e77cbb586c0807968f04f179f0848b60456e7929
57f906d to
7d81c82
Compare


Automated Release PR
0.149.0 (2026-11-16)
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
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), andreportTypes(list/retrieve types and per-version JSON Schema viareportTypes.versions.retrieve). Matching resource modules,api.md, exports, and skipped API resource tests are included; endpoint count in.stats.ymlrises 179 → 189.Vault items documentation and types change for checkout authorization fields (
amount_authorityvalues, charge-related optional fields) and item events gain optionalinclude_deletedfor 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.