Skip to content

release: 0.101.0 - #182

Merged
rgarcia merged 20 commits into
mainfrom
release-please--branches--main--changes--next--components--sdk
Sep 11, 2026
Merged

release: 0.101.0#182
rgarcia merged 20 commits into
mainfrom
release-please--branches--main--changes--next--components--sdk

Conversation

@stainless-app

@stainless-app stainless-app Bot commented Sep 5, 2026

Copy link
Copy Markdown
Contributor

Automated Release PR

0.101.0 (2026-09-11)

Features

  • Add config analysis lifecycle guarantees (2468a0a)
  • Brand origin TLS timeouts and classify provider failures (1f63d03)
  • Clarify proxy country defaults (43f283c)
  • Expose vault access in organization entitlements (0594999)
  • Integrate configurable vault providers across API and checkout (406359a)
  • Limit free organizations to three vaults (5c17e2d)
  • Populate safe failure reasons on invocation responses (e86903d)
  • Return vendor guidance with config registry recommendations (548c574)
  • Revert vendor guidance recommendations (6dbf3c0)
  • Support international ISP proxy countries (833e524)

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 payment-vault OAuth configuration and recovery semantics plus org vault limits; mostly OpenAPI-generated types but integrators must handle new statuses and entitlements fields.

Overview
Release 0.101.0 bumps the SDK and changelog and adds five configured API endpoints (158 → 163).

The headline capability is customer-managed vault providers: a new client.vaultProviderConfigs resource (create/retrieve/update/list/delete) for Link and AgentCard OAuth configs, with wallets and vault items able to bind provider_config by id or name and Link wallets supporting imported OAuth tokens alongside kernel-managed flow. Vault/card types gain recovery_required lifecycle states and stricter documented rules for updates, idempotent upserts, and deletes blocked by unresolved payments; free plans are documented as capped at three vaults, mirrored on org entitlements (vaults feature, max_vaults) and org limits (max_vaults, vaults_used).

Smaller contract updates: invocation responses document status_reason as a customer-safe failure summary and refine output semantics; config-registry analyses add expires_at and an expired status; proxy types document ISP countries (US, GB, FR, DE, SG) and optional country on residential/mobile; browser proxy_error telemetry adds provider_rejected and origin_tls_timeout.

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

Stainless-Generated-From: 6757a5098bb6f301f9675bd16893bf4e340fcad2
@stainless-app

stainless-app Bot commented Sep 5, 2026

Copy link
Copy Markdown
Contributor Author

🧪 Testing

To try out this version of the SDK:

npm install 'https://pkg.stainless.com/s/kernel-typescript/a008dfbe12ab150df7154f28127175e4ceee3816/dist.tar.gz'

Expires at: Sun, 11 Oct 2026 16:16:22 GMT
Updated at: Fri, 11 Sep 2026 16:16:22 GMT

@kernel-internal
kernel-internal Bot force-pushed the release-please--branches--main--changes--next--components--sdk branch from f382837 to 5cd35ce Compare September 5, 2026 18:43
Stainless-Generated-From: c92a896c34a16833a715e578fbfbaa4f487bcc1c
@stainless-app
stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--sdk branch from 5cd35ce to d8cc078 Compare September 5, 2026 20:26
@kernel-internal
kernel-internal Bot force-pushed the release-please--branches--main--changes--next--components--sdk branch from d8cc078 to b08dda4 Compare September 5, 2026 20:26
@kernel-internal
kernel-internal Bot force-pushed the release-please--branches--main--changes--next--components--sdk branch 2 times, most recently from a4c3dcb to d9cbba6 Compare September 9, 2026 17:05
@kernel-internal
kernel-internal Bot force-pushed the release-please--branches--main--changes--next--components--sdk branch from d9cbba6 to 62467a9 Compare September 9, 2026 23:58
@kernel-internal
kernel-internal Bot force-pushed the release-please--branches--main--changes--next--components--sdk branch from 62467a9 to 96355ee Compare September 10, 2026 18:13
@kernel-internal
kernel-internal Bot force-pushed the release-please--branches--main--changes--next--components--sdk branch from 96355ee to 2537ce5 Compare September 10, 2026 18:28
@kernel-internal
kernel-internal Bot force-pushed the release-please--branches--main--changes--next--components--sdk branch from 2537ce5 to 26021ca Compare September 10, 2026 19:56
@kernel-internal
kernel-internal Bot force-pushed the release-please--branches--main--changes--next--components--sdk branch from 26021ca to 7b7b5ab Compare September 10, 2026 20:22
@kernel-internal
kernel-internal Bot force-pushed the release-please--branches--main--changes--next--components--sdk branch from 7b7b5ab to 80d2140 Compare September 10, 2026 21:35
@kernel-internal
kernel-internal Bot force-pushed the release-please--branches--main--changes--next--components--sdk branch from 80d2140 to ec60ea6 Compare September 11, 2026 13:01

@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.

release checks are green. spot-checked the vault provider configuration resources, wallet authorization bindings, recovery states, and inclusion of the guidance revert. no blockers found in this release review; live SDK smoke tests were not run.

@rgarcia
rgarcia merged commit 88e5ccf into main Sep 11, 2026
11 checks passed
@kernel-internal

Copy link
Copy Markdown
Contributor

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