release: 0.96.0 - #162
Merged
stainless-app[bot] merged 2 commits intoAug 27, 2026
Merged
Conversation
Stainless-Generated-From: c9565b92fe48bc6ffd31ca18b75bc0535fc26324
kernel-internal
Bot
force-pushed
the
release-please--branches--main--changes--next
branch
from
August 27, 2026 00:00
8f1a20e to
826f5e4
Compare
Contributor
Author
|
🧪 Testing To try out this version of the SDK: Expires at: Sat, 26 Sep 2026 00:01:02 GMT |
Sayan-
approved these changes
Aug 27, 2026
Sayan-
left a comment
Collaborator
There was a problem hiding this comment.
Verified the generated surface matches the config registry rename in kernel/kernel#3594: endpoints under /config-registry with analyses as a subresource, the previous site-configs surface removed, and the release scoped to that single change. Checks green.
Contributor
Author
|
🤖 Release is at https://github.com/kernel/kernel-python-sdk/releases/tag/v0.96.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.96.0 (2026-08-27)
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
This is a breaking rename of a public SDK resource (client attribute, types, and method layout), so existing
site_configscall sites must be migrated even though behavior largely maps to the new config registry API.Overview
v0.96.0 replaces the site configs client surface with config registry, aligned with new
/config-registryHTTP routes.Integrators should use
client.config_registryinstead ofclient.site_configs. Lookup and resolve still exist but hit/config-registry/lookupand/config-registry/resolve, and resolve now returnsConfigRegistryResponse(replacingSiteConfigResponse). Domain recommendations are listed viaconfig_registry.list()onGET /config-registry(replacinglist_recommendations()). Historical analyses move toclient.config_registry.analyses(retrieve/liston/config-registry/analyses/{id}and/config-registry/analyses).List calls gain optional
search; recommendation list sorting can useanalysis_status.RecommendationSummaryaddsanalysis_idandanalysis_status. Related param and proxy helper types are renamed fromSiteConfig*toConfigRegistry*. Version metadata and generated tests/docs are updated accordingly; oldsite_configstests are removed.Reviewed by Cursor Bugbot for commit 826f5e4. Bugbot is set up for automated code reviews on this repo. Configure here.