chore: release #52
Merged
chore: release #52
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
![difizor[bot]](https://avatars.githubusercontent.com/in/748977?s=60&v=4){kind=small}
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
c44aff8 to
7cb0906
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #52 +/- ##
==========================================
+ Coverage 51.43% 52.75% +1.31%
==========================================
Files 364 364
Lines 43920 43926 +6
Branches 1468 1406 -62
==========================================
+ Hits 22591 23172 +581
+ Misses 21329 20754 -575 ☔ View full report in Codecov by Sentry. |
sunshinesmilelk
approved these changes
Aug 25, 2024
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
@difizen/[email protected]
Patch Changes
@difizen/[email protected]
Patch Changes
@difizen/[email protected]
Patch Changes
@difizen/[email protected]
Patch Changes
@difizen/[email protected]
Patch Changes
@difizen/[email protected]
Patch Changes
@difizen/[email protected]
Patch Changes
@difizen/[email protected]
Patch Changes
@difizen/[email protected]
Patch Changes
@difizen/[email protected]
Patch Changes