Releases: kernel/kernel-python-sdk
Release list
v0.107.0
0.107.0 (2026-09-16)
Features
- Classify unevaluable config registry targets (12ced86)
- Expose persistent Browser REPL through the API (755dba5)
- Return Link spend request errors directly (82d9f84)
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.106.0
0.106.0 (2026-09-16)
Full Changelog: v0.104.0...v0.106.0
Features
- Add processor-bound AgentCard preparation contracts (37d5e9c)
- Add start_url to browser session updates (82a475d)
- Polish and publish the Config Registry API (afe2fea)
- Square UKP and Hypeman placement load factors (76dee03)
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.104.0
0.104.0 (2026-09-15)
Features
- Expose the WebMCP
awaiting_submissionstatus (9b5cb34)
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.103.0
0.103.0 (2026-09-15)
Features
- chore(stlc): seal custom-code tracking files (4ce4ab9)
- Expose managed auth field input modes (c110358)
- Return working config registry configurations (0737fe9)
Bug Fixes
- disable automatic vault operation retries in SDKs (aad62f9)
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.102.0
0.102.0 (2026-09-14)
Features
- Accept a workload intent and use it to widen vendor coverage (39ffff8)
- Add guarded vault card fill operations (3927c96)
- Add single-use AgentCard prepare_checkout for Square (c439359)
- Allow replacing AgentCard cards after unknown creates (22a8731)
- Document punctuation key sequences (e7850fd)
- Honor managed auth browser regions (0fa2fa3)
- Reapply vendor guidance recommendations (dfcc7ec)
- Report proxy-restricted targets from config registry lookup (c276ebc)
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.101.0
0.101.0 (2026-09-11)
Features
- Add config analysis lifecycle guarantees (e0d9d71)
- Brand origin TLS timeouts and classify provider failures (b00a694)
- Clarify proxy country defaults (bb00cda)
- Expose vault access in organization entitlements (1c3b388)
- Integrate configurable vault providers across API and checkout (478bc09)
- Limit free organizations to three vaults (b0d5628)
- Populate safe failure reasons on invocation responses (7162cbb)
- Return vendor guidance with config registry recommendations (938e40b)
- Revert vendor guidance recommendations (adacc13)
- Support international ISP proxy countries (78adb8a)
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.100.0
0.100.0 (2026-09-04)
Features
- Fix vault provider errors and remove test card mode (043d252)
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.99.0
0.99.0 (2026-09-04)
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
v0.98.0
0.98.0 (2026-09-02)
Features
- Accept browser session name on all /browsers/{id_or_name} sub-resource routes (a60fa2b)
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.97.0
0.97.0 (2026-08-31)
Features
- Expose captcha task and challenge outcomes (42c33c6)
- Unify managed auth reauth eligibility and blockers (8e11fb2)
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