Skip to content

release: 0.122.0 - #200

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 (c203c7e)
  • Add feature-gated Korean ISP proxies (168ca36)
  • Describe vault fill as safe to retry (207ed0d)
  • Infer a challenge result for unobserved captcha providers in the relay (454206a)
  • Support proxy routes in browser pools (08ae962)

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 vault client-side encryption and changes documented semantics for egress allowlists, proxy routes, and vault fill retries; credential handling and browser networking behavior deserve extra review.

Overview
Release 0.122.0 bumps the SDK version and documents five API-facing features in generated types and client methods.

Vault credentials add Vaults.GetEncryptionKey and VaultEncryptionKey types so custom collection UIs can submit JWE ciphertext via encrypted_value on credential field create/update (mutually exclusive with value). Vault fill operation docs now state retries are safe after failure, unknown outcomes, or transport errors.

Browser networking updates clarify that proxy_routes apply from session start (including start_url) and are supported on browser pools (with proxy-v3); allowed_hosts can only be changed on browsers that were created with an allowlist, not added later. Pool create/update network docs mention proxy_routes and proxy-v3 provisioning.

Captcha telemetry extends challenge/solve events with captcha_provider, task_kind, and inferred challenge results (task_id vs challenge_id); captcha_type is deprecated.

Proxies add KR to managed ISP country codes across proxy and config-registry types.

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

Stainless-Generated-From: 7700e5e2fa1214255c2d57cea01ad303a7f6ba33
Stainless-Generated-From: c18071a4ec00082597312aba3de690121bc26ab1
@kernel-internal
kernel-internal Bot force-pushed the release-please--branches--main--changes--next branch from a99eaf4 to b07041c Compare October 8, 2026 19:08
Stainless-Generated-From: 840cf10eefa7d68365a20d156c560152b041a044
@kernel-internal
kernel-internal Bot force-pushed the release-please--branches--main--changes--next branch from b07041c to d7f2b16 Compare October 8, 2026 22:18
…e relay

Stainless-Generated-From: 3dce2de8e6fcbd2dec84a02bdd9a3a102072b42f
@kernel-internal
kernel-internal Bot force-pushed the release-please--branches--main--changes--next branch from d7f2b16 to dbe2f8d Compare October 9, 2026 12:16
Stainless-Generated-From: a978d73b39898255934c7aeeec542eae37d12294
@kernel-internal
kernel-internal Bot force-pushed the release-please--branches--main--changes--next branch from dbe2f8d to b42ea03 Compare October 9, 2026 15:56

@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 cd875f9 into main Oct 9, 2026
10 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