Skip to content

release: 0.122.0 - #190

Merged
rgarcia merged 6 commits into
mainfrom
release-please--branches--main--changes--next
Oct 9, 2026
Merged

rgarcia merged 6 commits into
mainfrom
release-please--branches--main--changes--next

Conversation

@kernel-internal

@kernel-internal kernel-internal Bot commented Oct 8, 2026 •

Copy link
Copy Markdown
Contributor

Automated Release PR

0.122.0 (2026-10-09)

Features

  • Accept client-encrypted credential values in vault items (a289cba)
  • Add feature-gated Korean ISP proxies (56785ca)
  • Describe vault fill as safe to retry (e419d6d)
  • Infer a challenge result for unobserved captcha providers in the relay (0e4734c)
  • Support proxy routes in browser pools (669ea52)

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 client-side encrypted credential submission and changes retry semantics for vault fill; networking and captcha event shape updates may affect integrators parsing telemetry or pool proxy configuration.

Overview
Release 0.122.0 bumps the SDK to match new API surface and documentation from the Kernel OpenAPI spec.

Vault credentials: Adds client.vaults.retrieve_encryption_key and the VaultEncryptionKey type so custom credential-collection UIs can fetch a vault public key and submit encrypted_value (JWE) on credential create/update instead of plaintext value. Credential field params now document mutual exclusivity between value and encrypted_value.

Vault fill behavior: SDK docs now state that fill is safe to retry after failure, unknown, or transport errors (fill does not submit the page), replacing prior guidance to avoid automatic retries.

Browser networking: proxy_routes are documented as supported on browser pools (with proxy-v3 / Envoy requirements), apply from session start including start_url, and pool create/update docs mention clearing routes via network: {proxy_routes: []}. allowed_hosts updates are clarified: only browsers created with an allowlist can change or remove it—not add one later.

Proxies: ISP proxy country lists now include KR (feature-gated on the API).

Captcha telemetry: Challenge/solve event models gain captcha_provider, task_kind, and inferred challenge results (with optional task_id instead of challenge_id); captcha_type is marked deprecated on those events.

Also: endpoint count 174→175, changelog entry, and generated tests for retrieve_encryption_key.

Reviewed by Cursor Bugbot for commit ead7682. Bugbot is set up for automated code reviews on this repo. Configure here.

Stainless-Generated-From: 79bf8dc71d82866e1c311325ca1fad69a10e1af5
Stainless-Generated-From: 1df9968d48c97505d364e1d1dadc0386e4e71eb1
@kernel-internal
kernel-internal Bot force-pushed the release-please--branches--main--changes--next branch from 2ed84eb to ea0fb0d Compare October 8, 2026 19:08
Stainless-Generated-From: 1764fa39f87baa779274e940153ed43cd3325574
@kernel-internal
kernel-internal Bot force-pushed the release-please--branches--main--changes--next branch from ea0fb0d to 955bada Compare October 8, 2026 22:18
…e relay

Stainless-Generated-From: 0e92268c9f54dda6b9512e74bff0cebb24f4d759
@kernel-internal
kernel-internal Bot force-pushed the release-please--branches--main--changes--next branch from 955bada to 505e0dd Compare October 9, 2026 12:16
Stainless-Generated-From: 07412a4aeca64157ed1cf0679c95fda486a9b860
@kernel-internal
kernel-internal Bot force-pushed the release-please--branches--main--changes--next branch from 505e0dd to ead7682 Compare October 9, 2026 15:57

@rgarcia rgarcia left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed: vault encryption key method/type and encrypted_value on credential field input/update are modeled correctly.

@rgarcia
rgarcia merged commit 84acd58 into main Oct 9, 2026
11 checks passed
@kernel-internal

Copy link
Copy Markdown
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant