Repository navigation
release: 0.128.0 - #198
Open
kernel-internal[bot] wants to merge 2 commits into
Open
release: 0.128.0#198kernel-internal[bot] wants to merge 2 commits into
kernel-internal[bot] wants to merge 2 commits into
Conversation
Stainless-Generated-From: f9646cbea73c1147aefb46dce6e811b9683125e0
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.128.0 (2026-10-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
Medium Risk
Renaming proxy method parameters from
idtoid_or_namebreaks existing callers using keyword arguments; proxy name resolution can surface new ambiguous-name API errors.Overview
Release 0.128.0 bumps package version metadata and changelog; the functional SDK changes are proxy addressing and tighter Link card type docs.
Proxies now use an
id_or_namepath parameter on retrieve, update, delete, and check (sync and async). Callers can pass a proxy ID or exact name; docs note ID precedence and a400withambiguous_proxy_namewhen a name matches multiple proxies. The Python argument was renamed fromidtoid_or_name, which is a breaking change for code using theid=keyword.Vault Link card specs (
LinkCardVaultItemSpecand param) now documentamountas capped at 50000 minor units only, removing the previous split between Link Pay Token (500000) and virtual-card (50000) limits.api.mdand proxy tests were updated to match the new parameter name.Reviewed by Cursor Bugbot for commit 5281a58. Bugbot is set up for automated code reviews on this repo. Configure here.