Skip to content

release: 0.109.0 - #186

Merged
stainless-app[bot] merged 4 commits into
mainfrom
release-please--branches--main--changes--next
Sep 17, 2026
Merged

stainless-app[bot] merged 4 commits into
mainfrom
release-please--branches--main--changes--next

Conversation

@stainless-app

@stainless-app stainless-app Bot commented Sep 17, 2026 •

Copy link
Copy Markdown
Contributor

Automated Release PR

0.109.0 (2026-09-17)

Features

  • Accept opaque AgentCard vaulted card IDs (5cfcedd)
  • Expose organization-wide concurrent browser capacity (6367486)
  • Preserve credential field order (3038f83)

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
Credential vault Fields switching from map to slice is a breaking Go API change for integrators; vault/payment and concurrency limit types touch capacity-sensitive workflows.

Overview
Release v0.109.0 bumps package/docs version strings and documents three API-facing SDK updates.

OrgLimits from GET org/limits now includes concurrent_sessions_used and concurrent_sessions_available, so callers can read org-wide browser concurrency usage and headroom alongside existing plan limits.

Credential vault item field definitions change from a map keyed by name to an ordered slice with an explicit required name on each CredentialVaultFieldDefinition / input param, matching API behavior where collection form field order is preserved.

AgentCard vault specs clarify that card_id is an opaque AgentCard wallet card identifier to pass through unchanged (no assumed format).

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

Stainless-Generated-From: c851fce5b96b2d6a6cbc94ee40d24e6f589d99e9
@stainless-app

stainless-app Bot commented Sep 17, 2026 •

Copy link
Copy Markdown
Contributor Author

🧪 Testing

To try out this version of the SDK:

Download and unzip: 'https://pkg.stainless.com/s/kernel-go/5cfceddfb1ea8ad60df078bd8e89b11ca1aaa8d2/source.zip'. Run 'go mod edit -replace github.com/kernel/kernel-go-sdk=/path/to/unzipped_directory'.

Expires at: Sat, 17 Oct 2026 21:36:32 GMT
Updated at: Thu, 17 Sep 2026 21:36:32 GMT

@kernel-internal
kernel-internal Bot force-pushed the release-please--branches--main--changes--next branch from 94011f3 to 29bf973 Compare September 17, 2026 20:02
Stainless-Generated-From: e2f4e92a7b1cdaf2b5b27fb94b0d0b00728641c9
@stainless-app
stainless-app Bot force-pushed the release-please--branches--main--changes--next branch from 29bf973 to 373cdbf Compare September 17, 2026 21:11
@kernel-internal
kernel-internal Bot force-pushed the release-please--branches--main--changes--next branch from 373cdbf to 4536455 Compare September 17, 2026 21:11
Stainless-Generated-From: c3ba93d5808d09ce6dec695fd76b45939abae2a7
@stainless-app
stainless-app Bot force-pushed the release-please--branches--main--changes--next branch from 4536455 to d90f2eb Compare September 17, 2026 21:36
@kernel-internal
kernel-internal Bot force-pushed the release-please--branches--main--changes--next branch from d90f2eb to 12f9108 Compare September 17, 2026 21:37

@masnwilliams masnwilliams 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 contents and generated credential field-order types verified; checks are green.

@stainless-app
stainless-app Bot merged commit 5c91a27 into main Sep 17, 2026
10 checks passed
@stainless-app

stainless-app Bot commented Sep 17, 2026

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