Prepare for v0.10.0#232
Merged
stefanvanburen merged 1 commit intomainfrom Apr 28, 2026
Merged
Conversation
Based on [this comment][1], I think our next release ought to be `v0.10.0`. [1]: #230 (comment) Signed-off-by: Stefan VanBuren <svanburen@buf.build>
Collaborator
|
Thanks for checking on this. I was thinking patch for the How does that sound? |
Member
Author
anuraaga
approved these changes
Apr 28, 2026
Collaborator
anuraaga
left a comment
anuraaga
left a comment
There was a problem hiding this comment.
Thanks for catching that! I read the previous release notes but should have looked through the commits closer, I mixed up compression and codec. Definitely not a patch release.
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.
Based on this comment, I think our next release ought to be
v0.10.0.