Conversation
|
🧪 Testing To try out this version of the SDK, run: Expires: Fri, 24 Oct 2025 20:30:17 GMT |
There was a problem hiding this comment.
Performed full review of 7030d45...c6ce4a9
Analysis
Based on the provided analysis, there do not appear to be any significant architectural issues with this pull request. The analysis shows that the implementation of the "Per Invocation Logs" functionality follows good practices and maintains consistency. The reviewer actually noted several strengths and no specific concerns with the implementation.
Since you specifically asked for potential issues, I'll note that the absence of identified problems in the architectural analysis suggests this is a well-executed change that doesn't introduce architectural risks.
Tip
⚡ Quick Actions
This review was generated by Mesa.
Actions:
Slash Commands:
/review- Request a full code review/review latest- Review only changes since the last review/describe- Generate PR description. This will update the PR body or issue comment depending on your configuration/help- Get help with Mesa commands and configuration options
10 files reviewed | 0 comments | Review on Mesa | Edit Reviewer Settings
Release version edited manuallyThe Pull Request version has been manually set to If you instead want to use the version number |
c6ce4a9 to
291f434
Compare
|
🤖 Release is at https://github.com/onkernel/kernel-python-sdk/releases/tag/v0.11.3 🌻 |
Automated Release PR
0.11.3 (2025-09-24)
Full Changelog: v0.11.2...v0.11.3
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
TL;DR
This is an automated release that bumps the package version to
0.11.3and introduces a new feature for streaming logs on a per-invocation basis.Why we made these changes
This change provides more granular observability into the system. By allowing users to access logs for a specific invocation, it becomes much easier to debug and monitor individual API calls without needing to sift through system-wide logs.
What changed?
invocationsresource to stream logs for a specific invocation.api.md), and parameter types (invocation_follow_params.py) to support the new feature.test_invocations.pyto validate the per-invocation logging functionality.0.11.3inpyproject.toml,CHANGELOG.md, and other release-related files.Description generated by Mesa. Update settings