Repository navigation
release: 0.131.0 - #211
release: 0.131.0#211
Conversation
…tro-api Stainless-Generated-From: b3b0583c655a6297a1ea4a2ab6e6f4f90f9e743d
Rebase the CLI coverage branch on main and regenerate bot-only branches on conflict
1bc2ab1 to
eecefc9
Compare
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 eecefc9. Configure here.
| fi | ||
| gh auth setup-git | ||
| git push origin cli-coverage-update | ||
| git push --force-with-lease="cli-coverage-update:$UPDATE_SHA" origin cli-coverage-update |
There was a problem hiding this comment.
Force-push discards reviewer branch commits
Medium Severity
The publish job always recreates cli-coverage-update from MAIN_SHA and force-pushes. Human commits that rebase cleanly are squashed into a bot commit, and the allowlist drops reviewer files outside go.mod, go.sum, and .go under cmd/ and pkg/. The human-author check only runs when rebase conflicts.
Additional Locations (2)
Reviewed by Cursor Bugbot for commit eecefc9. Configure here.
rgarcia
left a comment
There was a problem hiding this comment.
Release 0.131.0: vault passkey operations (arm_passkey, register_passkey, disarm_passkey) from kernel/kernel#4767.
|
🤖 Release is at https://github.com/kernel/kernel-go-sdk/releases/tag/v0.131.0 🌻 |


Automated Release PR
0.131.0 (2026-10-26)
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
New vault passkey/WebAuthn operation types affect security-sensitive credential flows; CLI coverage workflow changes alter branch rewrite and force-push behavior on kernel/cli.
Overview
Release 0.131.0 bumps the package version and changelog; the substantive API change is vault passkey browser operations on credential vault items.
Clients can call
VaultItem.PerformOperationwith new request variantsarm_passkey,register_passkey, anddisarm_passkey(browser session + optional field), and handlePasskeyVaultItemOperationResult(armed/disarmed, optionalrp_id). Available-operation metadata and passkey field docs now point to these operations instead of page fill.api.mdlists the new param and response types.Separately, the update-cli-coverage workflow rebases
cli-coverage-updateontomain, regenerates bot-only branches frommainon rebase conflicts, snapshots diffs againstmain_sha(not a post-merge agent base), applies publish changes on a fresh branch from main, and pushes with--force-with-lease; security tests were updated to match.Reviewed by Cursor Bugbot for commit eecefc9. Bugbot is set up for automated code reviews on this repo. Configure here.