Skip to content

release: 0.66.0#124

Merged
stainless-app[bot] merged 4 commits into
mainfrom
release-please--branches--main--changes--next--components--sdk
Jun 10, 2026
Merged

release: 0.66.0#124
stainless-app[bot] merged 4 commits into
mainfrom
release-please--branches--main--changes--next--components--sdk

Conversation

@stainless-app

@stainless-app stainless-app Bot commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

Automated Release PR

0.66.0 (2026-06-10)

Full Changelog: v0.65.0...v0.66.0

Features

  • Add org-level default per-project concurrency cap (b5aa208)
  • Support updating browser session name and tags via PATCH (608cb36)

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

Low Risk
Additive OpenAPI-generated client surface and optional PATCH fields; no changes to auth or core request plumbing beyond new routes.

Overview
Release 0.66.0 bumps the package and OpenAPI metadata (119 endpoints) and documents two API-facing SDK updates.

Adds client.organization.limits with retrieve() and update() for GET / PATCH /org/limits, exposing org-wide max_concurrent_sessions and the configurable default_project_max_concurrent_sessions default for projects without their own cap.

Browser session PATCH now supports name and tags on BrowserUpdateParams (clear name with "", replace or clear tags with a full map or {}). Create-time docs for name/tags are updated to say they can be changed later via PATCH /browsers/{id_or_name}.

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

@firetiger-agent

Copy link
Copy Markdown

Firetiger deploy monitoring skipped

This PR didn't match the auto-monitor filter configured on your GitHub connection:

PRs in the kernel, infra, hypeman, and hypeship repos. kernel is a ~mono repo with many logical services underneath, ensure to focus on the implicated service for the PR

Reason: This is an automated release PR for the kernel-node-sdk repository, which appears to be a Node.js SDK package rather than a deployable service within the kernel mono repo; clarify if this should trigger deploy monitoring.

To monitor this PR anyway, reply with @firetiger monitor this.

@stainless-app

stainless-app Bot commented Jun 9, 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/608cb360a226f5968f253ea3ab928231f649c12e/dist.tar.gz'

Expires at: Fri, 10 Jul 2026 20:46:14 GMT
Updated at: Wed, 10 Jun 2026 20:46:14 GMT

@stainless-app stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--sdk branch from 4972bc6 to 3c53a0e Compare June 9, 2026 21:32
@stainless-app stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--sdk branch from 3c53a0e to ba1575f Compare June 10, 2026 20:42
@stainless-app stainless-app Bot merged commit 61f4d3a into main Jun 10, 2026
11 checks passed
@stainless-app

stainless-app Bot commented Jun 10, 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