Repository navigation
Releases: kernel/kernel-node-sdk
Release list
v0.131.0
0.131.0 (2026-10-26)
Features
- Arm vault passkeys in browsers and sign WebAuthn requests in metro-api (1423392)
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
v0.130.0
0.130.0 (2026-10-24)
Features
- Support Link recurring spend requests on vault Link cards (6becbe5)
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
v0.129.0
0.129.0 (2026-10-21)
Features
- chore(stlc): seal custom-code tracking files (c6f4ec6)
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
v0.128.0
0.128.0 (2026-10-19)
Features
- Add browser location session policy (942881d)
- chore(stlc): seal custom-code tracking files (784dff8)
- Fence browser allowlist updates with revision checks (733ca11)
- Support existing-user AgentCard wallet imports (e84e82f)
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
v0.127.0
0.127.0 (2026-10-16)
Features
- Add atomic preconditions to pool network updates (50d68f4)
- Add passkey credential fields and PATCH field add/remove (d1001f3)
- Allow replacing vault cards whose provider outcome is unknown (060038b)
- chore(stlc): seal custom-code tracking files (2b47c61)
- Classify text captchas as token tasks and Binance as a provider (0974d4f)
- Deliver Kernel card details through fill (03d2609)
- Raise Kernel card amount cap to $10,000 (1f992aa)
- Remove Link expires_at, return 400 for missing credential values, and log fill failures (8dea4a0)
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
v0.126.0
0.126.0 (2026-10-14)
Features
- support Link Pay Tokens when authorizing Link cards at checkout (9b8ccd8)
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
v0.125.0
0.125.0 (2026-10-13)
Features
- chore(stlc): seal custom-code tracking files (635766d)
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
v0.124.0
0.124.0 (2026-10-13)
Features
- Accept intent creation without a fixed status (7cf9f3d)
- Complete Visa vault verification and transaction reporting (41d139b)
Bug Fixes
- seal browser pool acquire SDK results (05baf34)
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
v0.123.0
0.123.0 (2026-10-09)
Features
- Add video_memory to request the 4GiB VRAM GPU browser tier (364255d)
- Filter the telemetry SSE stream by event type (2ccedc6)
- Fix 1Password fill classification for repeat fills and unconfirmed submits (4133242)
- Support egress allowlists on browser pools (41f4980)
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
v0.122.0
0.122.0 (2026-10-09)
Features
- Accept client-encrypted credential values in vault items (78ee783)
- Add feature-gated Korean ISP proxies (96d63e2)
- Describe vault fill as safe to retry (b96e6ca)
- Infer a challenge result for unobserved captcha providers in the relay (84022be)
- Support proxy routes in browser pools (e5b2ffc)
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