chore: version packages #1413
Merged
chore: version packages #1413
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
People can be co-author:
|
|
Size Change: 0 B Total Size: 68.9 kB ℹ️ View Unchanged
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1413 +/- ##
=======================================
Coverage 73.85% 73.85%
=======================================
Files 70 70
Lines 589 589
Branches 131 131
=======================================
Hits 435 435
Misses 142 142
Partials 12 12
|
manudeli
commented
Jan 13, 2025
There was a problem hiding this comment.
@LineGu @lucas0530 This is important change! Thanks for issuing 👀🦅
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@suspensive/[email protected]
Patch Changes
ce3cb11Thanks @manudeli! - fix(react): prevent rendering fallback if not shouldCatch error@suspensive/[email protected]
Patch Changes
ce3cb11]:@suspensive/[email protected]
Patch Changes
ce3cb11]:@suspensive/[email protected]
Patch Changes
ce3cb11]:@suspensive/[email protected]