release: 0.58.0#111
Merged
stainless-app[bot] merged 6 commits intoMay 27, 2026
Merged
Conversation
|
Firetiger deploy monitoring skipped This PR didn't match the auto-monitor filter configured on your GitHub connection:
Reason: This is an automated release PR for the Node SDK, not a change to kernel API endpoints or Temporal workflows. To monitor this PR anyway, reply with |
Contributor
Author
|
🧪 Testing To try out this version of the SDK: Expires at: Fri, 26 Jun 2026 17:10:11 GMT |
de451cc to
9e5b741
Compare
8e9f7b1 to
bb0806f
Compare
added 2 commits
May 27, 2026 14:55
This SDK repo declares Yarn as its package manager and Stainless updates yarn.lock when dependency metadata changes. Keeping package-lock.json created a second lockfile source of truth. The stale npm lockfile caused npm ci to reject the release branch after Stainless bumped tsc-multi from v1.1.9 to v1.1.11 in package.json and yarn.lock but not package-lock.json. Remove package-lock.json so future generated release PRs inherit the Yarn-owned dependency state instead of needing manual npm lockfile syncs.
Refresh yarn.lock after removing package-lock.json so the Yarn-owned install path passes yarn install --frozen-lockfile. The refresh adds missing direct lock entries for busboy, @types/busboy, and streamsearch.
Contributor
Author
|
🤖 Release is at https://github.com/kernel/kernel-node-sdk/releases/tag/v0.58.0 🌻 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated Release PR
0.58.0 (2026-05-27)
Full Changelog: v0.57.0...v0.58.0
Features
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
New API key client surface touches credential management; telemetry type/doc changes may affect consumers relying on removed
BrowserTelemetryRequestConfig.Overview
Release 0.58.0 bumps the package and OpenAPI metadata (117 configured endpoints) and documents the release in
CHANGELOG.md.The SDK gains a first-class
client.apiKeysresource for org-scoped API key lifecycle (/org/api_keys: create with one-time plaintextkey, retrieve, update name, list, delete), reflected inapi.mdand exports.Browser telemetry request modeling is updated:
BrowserTelemetryRequestConfigis removed from the public API docs in favor of create/update params that support anenabledshortcut plus per-categorybrowsersettings (aligned with OpenAPI/SDK metadata fixes noted in the changelog).Reviewed by Cursor Bugbot for commit 093cadd. Bugbot is set up for automated code reviews on this repo. Configure here.