Release 0.24.0#453
Merged
Merged
Conversation
New features and changes have landed, making it a good time to cut a release. Further feature proposals can be incorporated in future releases. One of the requirements for the official SDK to move from Tier 3 to Tier 2 is reaching v1.0, and that milestone is now quite close. The main considerations for v1.0 are API stability and minimizing breaking changes. Based on the work in my local branch, a path toward Tier 1 is already becoming clear from my perspective, and this release is part of the work to prepare for Tier 2.
atesgoral
approved these changes
Jul 11, 2026
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
2 participants
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.
New features and changes have landed, making it a good time to cut a release. Further feature proposals can be incorporated in future releases.
One of the requirements for the official SDK to move from Tier 3 to Tier 2 is reaching v1.0, and that milestone is now quite close.
The main considerations for v1.0 are API stability and minimizing breaking changes. A path toward Tier 1 is already becoming clear, and this release is part of the work to prepare for Tier 2.
Checklist