Repository navigation
release: 0.133.0 - #203
Open
kernel-internal[bot] wants to merge 2 commits into
Open
release: 0.133.0#203kernel-internal[bot] wants to merge 2 commits into
kernel-internal[bot] wants to merge 2 commits into
Conversation
…ests Stainless-Generated-From: d8f3e64609f69a8484f189c430cc0dc307ee82a2
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.133.0 (2026-10-27)
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
Adds payment and vault-item surface area (enrollment links, method removal, purchase funding binding); mostly additive OpenAPI-generated types but affects how integrators model wallets and checkout.
Overview
Release 0.133.0 extends the vault API for multi-card Kernel wallets and wallet-scoped purchases.
Callers can manage cards on a connected Kernel wallet via new vault item operations
add_payment_method(hosted card enrollment link) andremove_payment_method(payment_method_id), with typed request/result models andperform_operationoverloads on sync/asyncItemsResource.VaultPaymentMethodnow carries enrollment status, optional action/expires_at, and clearer default-card semantics.A new
payment_requestvault item type (Link and Kernel specs) models purchases parented by a wallet, withupsert/updatesupport alongside existing card/credential flows. Kernel card specs and state gain optionalpayment_method_idandfunding_statusso purchases are bound to a specific wallet payment method. Docs and credential guidance now steer checkout toward wallet, payment_request, and card items instead of credentials alone.Reviewed by Cursor Bugbot for commit 629aab1. Bugbot is set up for automated code reviews on this repo. Configure here.