release: 0.68.0#126
Open
stainless-app[bot] wants to merge 3 commits into
Open
Conversation
|
Firetiger deploy monitoring skipped This PR didn't match the auto-monitor filter configured on your GitHub connection:
Reason: This PR is for the kernel-node-sdk repository, not the kernel, infra, hypeman, or hypeship repos specified in the filter. To monitor this PR anyway, reply with |
Contributor
Author
|
🧪 Testing To try out this version of the SDK: Expires at: Sun, 12 Jul 2026 16:09:42 GMT |
95dedf9 to
9df1a52
Compare
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.68.0 (2026-06-12)
Full Changelog: v0.67.0...v0.68.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
Changes org API key list/retrieve behavior and types; new params are opt-in but callers in security-sensitive flows should verify they still handle 404 vs audit responses correctly.
Overview
Release 0.68.0 ships OpenAPI-driven updates for org API key audit visibility.
APIKeyresponses now includedeleted_atand a derivedstatus(active|expired|deleted). List and retrieve accept optionalinclude_deletedso soft-deleted keys can be included for audit; without it, deleted keys stay hidden (retrieve still 404s by default).client.apiKeys.retrievenow takes an optional query object (APIKeyRetrieveParams) before request options, matching other list-style methods. Version metadata (package.json,CHANGELOG, OpenAPI stats) is bumped to 0.68.0.Reviewed by Cursor Bugbot for commit 9df1a52. Bugbot is set up for automated code reviews on this repo. Configure here.