Repository navigation
release: 0.128.0 - #214
Open
kernel-internal[bot] wants to merge 2 commits into
Open
release: 0.128.0#214kernel-internal[bot] wants to merge 2 commits into
kernel-internal[bot] wants to merge 2 commits into
Conversation
Stainless-Generated-From: 8fdf6e377bf2afc1c999d603c17c45ec08e02177
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
Proxy callers can address resources by name but may hit ambiguous-name errors; Link card amount docs now reflect a lower documented cap, which may surprise integrators who relied on the higher Link Pay Token limit in comments.
Overview
Release 0.128.0 updates the Node SDK to match API contract changes for proxies and vault Link cards.
Proxies —
retrieve,update,delete, andchecknow take anidOrNamepath segment (/proxies/{id_or_name}) instead of ID-only. Docs describe exact-name lookup (database collation), ID precedence when a value could be both, andambiguous_proxy_name(400) when a name matches more than one proxy.api.mdand proxy tests/examples were updated accordingly.Vault —
LinkCardVaultItemSpec.amountis documented as at most 50,000 minor units only; the previous split between Link Pay Token (500,000) and virtual-card (50,000) limits was removed from the type comments.Also includes the usual release metadata (
package.json,version.ts, changelog, release-please manifest).Reviewed by Cursor Bugbot for commit b6920fc. Bugbot is set up for automated code reviews on this repo. Configure here.