chore(release): merge main into develop - #635
Merged
Merged
Conversation
tomymaritano
disabled auto-merge
August 28, 2026 16:47
tomymaritano
enabled auto-merge
August 28, 2026 16:47
tomymaritano
approved these changes
Aug 28, 2026
tomymaritano
disabled auto-merge
August 28, 2026 18:59
Collaborator
|
@coderabbitai approve |
tomymaritano
enabled auto-merge
August 28, 2026 19:00
✅ Action performedComments resolved. Approval is disabled; enable |
Contributor
Author
|
🎉 This PR is included in version 0.23.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
1 participant
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.
Back-merge of v0.22.0 so main stays an ancestor of develop and the next promotion PR is not stuck at BEHIND.
Merge this with a merge commit. A squash replays the content as a new commit and does not establish ancestry.