Repository navigation
chore(release): prepare 0.3.0 - #12
Merged
Merged
Conversation
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.
Summary
Prepare Python SDK 0.3.0 for the new Forward Credential update and Usage APIs, Managed Session cancellation, and deployment-scoped Run queries. Update the project and lockfile root versions and publish the existing changelog entries under 0.3.0.
This branch includes the merged integration-test fix that allows a session to reuse skill content across turns.
Verification
uv sync --python 3.12 --extra dev --extra release --lockeduv run --no-sync make lint typecheck test docs-check builduv run --no-sync python -m twine check dist/*The API implementation on GitHub main passed the latest internal CN and Global integration run, including both resource lifecycle scenarios. Batch and Dream remained excluded. This PR only changes release metadata and documentation; the release workflow will separately verify public package installation after publication.
Impact
The changelog retains an empty Unreleased section. No dependencies or API implementation change in this PR.