feat: update documentation to force a release#581
Merged
chrisrolfe198 merged 1 commit intomainfrom Apr 2, 2026
Merged
Conversation
chrisrolfe198
requested review from
AlanFnz,
Amin52J,
Mukesh-FN,
lizzielerwill-ctrl and
renejfc
as code owners
AlanFnz
approved these changes
Apr 2, 2026
commit: |
Contributor
|
🎉 This PR is included in version 2.55.0 🎉 The release is available on: 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
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.
What
When I merged #580 I didn't ensure that it had a semantic commit message so that means a release didn't happen. I've updated the async example to contain renderEmptyState which is a good practice mostly to force the new release
Media
Why
How