chore(repo): version packages for canary (canary) #605
Conversation
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
knock-eng-bot
requested review from
connorlindsey and
kylemcd
and removed request for
a team
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 4 Skipped Deployments
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## canary #605 +/- ##
=========================================
Coverage ? 61.39%
=========================================
Files ? 175
Lines ? 6805
Branches ? 759
=========================================
Hits ? 4178
Misses ? 2601
Partials ? 26 🚀 New features to boost your workflow:
|
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 canary, this PR will be updated.
canaryis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitoncanary.Releases
@knocklabs/client@0.14.10-canary.2
Patch Changes
@knocklabs/expo@0.3.22-canary.2
Patch Changes
@knocklabs/react@0.7.16-canary.2
Patch Changes
@knocklabs/react-core@0.6.14-canary.2
Patch Changes
@knocklabs/react-native@0.6.22-canary.2
Patch Changes
client-example@0.3.12-canary.2
Patch Changes
@knocklabs/expo-example@0.1.35-canary.2
Patch Changes
guide-example@0.0.17-canary.2
Patch Changes
ms-teams-connect-example@0.0.4-canary.2
Patch Changes
nextjs-app-dir-example@0.0.3-canary.2
Patch Changes
nextjs-example@1.1.19-canary.2
Patch Changes
@knocklabs/react-native-example@1.4.35-canary.2
Patch Changes
slack-connect-example@0.3.3-canary.2
Patch Changes
slack-kit-example@0.4.1-canary.2
Patch Changes