Skip to content

release: 0.67.0#125

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

release: 0.67.0#125
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 11, 2026

Copy link
Copy Markdown
Contributor

Automated Release PR

0.67.0 (2026-06-11)

Full Changelog: v0.66.0...v0.67.0

Features

  • Add project_id SDK client option mapped to X-Kernel-Project-Id (2de4df2)

Documentation

  • api: correct project-scoping descriptions in OpenAPI spec (5320bde)

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
Sending X-Kernel-Project-Id on every request changes how the API resolves resources; wrong or missing project IDs could break existing integrations that assumed org-wide scope.

Overview
Release 0.67.0 adds optional projectID on the Kernel client (ClientOptions, constructor default null, preserved in withOptions). Every API request now includes X-Kernel-Project-Id from that value so callers can target a specific project.

Generated API docs/JSDoc are updated to describe project scoping instead of org ownership: list/create helpers for proxies, credentials, extensions, and browser pools, plus proxy selection on auth connections, browser pools, and browser create now say resources must live in the same project as the referencing resource.

Version metadata (package.json, CHANGELOG.md, .stats.yml, OpenAPI spec hash) bumps to 0.67.0.

Reviewed by Cursor Bugbot for commit a36a6e6. 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 (a Node.js SDK client library), which is not a core service requiring deploy monitoring under the specified filter.

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

@stainless-app stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--sdk branch from 720eb6e to 05d10f9 Compare June 11, 2026 21:01
@stainless-app stainless-app Bot changed the title release: 0.66.1 release: 0.67.0 Jun 11, 2026
@stainless-app stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--sdk branch from 05d10f9 to 056df15 Compare June 11, 2026 21:02
@stainless-app

stainless-app Bot commented Jun 11, 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/2de4df21f6d2d2dd570bed37c4da34b2df34cf83/dist.tar.gz'

Expires at: Sat, 11 Jul 2026 21:46:36 GMT
Updated at: Thu, 11 Jun 2026 21:46:36 GMT

@stainless-app stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--sdk branch from 056df15 to a36a6e6 Compare June 11, 2026 21:45
@IlyaasK IlyaasK self-requested a review June 12, 2026 14:37

@IlyaasK IlyaasK left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

lgtm

@stainless-app stainless-app Bot merged commit a6dda60 into main Jun 12, 2026
11 checks passed
@stainless-app

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