chore(repo): version packages for rc (rc)#1034
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
kylemcd
approved these changes
Jul 10, 2026
kylemcd
approved these changes
Jul 10, 2026
kylemcd
left a comment
Member
There was a problem hiding this comment.
RC version bumps look correct (0.22.0-rc.0 line, rc dist-tag).
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## rc #1034 +/- ##
=====================================
Coverage ? 66.02%
=====================================
Files ? 213
Lines ? 10499
Branches ? 1509
=====================================
Hits ? 6932
Misses ? 3542
Partials ? 25 |
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
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 rc, this PR will be updated.
rcis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonrc.Releases
@knocklabs/client@0.22.0-rc.0
Minor Changes
d2f7948: Make the client do nothing (instead of throwing or making requests) when there's no signed-in user, and add tools to manage sign-in state.
Knock.logout()clears the user and disconnects everything: the websocket, the token-refresh timer, and the page-visibility listener.knock.authStatus("authenticated"or"unauthenticated") and a subscribableknock.authStoreto check or react to whether a user is signed in.markAs*/markAll*/fetchNextPage(they also skip the optimistic UI update).fetch/subscribeand the step actions. These previously threw, which could crash the app when Guides rendered before a user was set.authCheck(returns "not connected"),getChannels/getTeams(return empty), andmessages.batchUpdateStatuses(returns[]).historypatch used for location tracking broke when a Guide provider remounted.@knocklabs/expo@0.7.0-rc.0
Minor Changes
d2f7948: Add an
enabledprop toKnockProvider(and anenabledoption touseAuthenticatedKnockClient).When
enabledisfalse, the provider still renders its children but the Knock client sits idle: no identify call, no API requests, no websocket. Set it totrueand it connects like a login; set it back tofalseand it disconnects and clears its data like a logout. It defaults totrue, so existing code is unaffected.Use this instead of conditionally mounting
KnockProvider, for example to wait for a user token that loads asynchronously:Also fixed:
useFeedSettingsno longer callsGET /v1/users/undefined/feeds/.../settingswhen there's no user.KnockProvidernow disconnects its client (websocket, token-refresh timer, listener) when it unmounts, instead of leaving them running.d2f7948: Add
useKnockAuthState()and make Slack, MS Teams, and Expo respond to sign-in changes.useKnockAuthState(knock)hook re-renders when the user signs in, signs out, or switches.Patch Changes
@knocklabs/react@0.12.0-rc.0
Minor Changes
d2f7948: Add an
enabledprop toKnockProvider(and anenabledoption touseAuthenticatedKnockClient).When
enabledisfalse, the provider still renders its children but the Knock client sits idle: no identify call, no API requests, no websocket. Set it totrueand it connects like a login; set it back tofalseand it disconnects and clears its data like a logout. It defaults totrue, so existing code is unaffected.Use this instead of conditionally mounting
KnockProvider, for example to wait for a user token that loads asynchronously:Also fixed:
useFeedSettingsno longer callsGET /v1/users/undefined/feeds/.../settingswhen there's no user.KnockProvidernow disconnects its client (websocket, token-refresh timer, listener) when it unmounts, instead of leaving them running.d2f7948: Add
useKnockAuthState()and make Slack, MS Teams, and Expo respond to sign-in changes.useKnockAuthState(knock)hook re-renders when the user signs in, signs out, or switches.Patch Changes
@knocklabs/react-core@0.14.0-rc.0
Minor Changes
d2f7948: Add an
enabledprop toKnockProvider(and anenabledoption touseAuthenticatedKnockClient).When
enabledisfalse, the provider still renders its children but the Knock client sits idle: no identify call, no API requests, no websocket. Set it totrueand it connects like a login; set it back tofalseand it disconnects and clears its data like a logout. It defaults totrue, so existing code is unaffected.Use this instead of conditionally mounting
KnockProvider, for example to wait for a user token that loads asynchronously:Also fixed:
useFeedSettingsno longer callsGET /v1/users/undefined/feeds/.../settingswhen there's no user.KnockProvidernow disconnects its client (websocket, token-refresh timer, listener) when it unmounts, instead of leaving them running.d2f7948: Add
useKnockAuthState()and make Slack, MS Teams, and Expo respond to sign-in changes.useKnockAuthState(knock)hook re-renders when the user signs in, signs out, or switches.Patch Changes
@knocklabs/react-native@0.10.0-rc.0
Minor Changes
d2f7948: Add an
enabledprop toKnockProvider(and anenabledoption touseAuthenticatedKnockClient).When
enabledisfalse, the provider still renders its children but the Knock client sits idle: no identify call, no API requests, no websocket. Set it totrueand it connects like a login; set it back tofalseand it disconnects and clears its data like a logout. It defaults totrue, so existing code is unaffected.Use this instead of conditionally mounting
KnockProvider, for example to wait for a user token that loads asynchronously:Also fixed:
useFeedSettingsno longer callsGET /v1/users/undefined/feeds/.../settingswhen there's no user.KnockProvidernow disconnects its client (websocket, token-refresh timer, listener) when it unmounts, instead of leaving them running.d2f7948: Add
useKnockAuthState()and make Slack, MS Teams, and Expo respond to sign-in changes.useKnockAuthState(knock)hook re-renders when the user signs in, signs out, or switches.Patch Changes
client-example@0.3.60-rc.0
Patch Changes
@knocklabs/expo-example@1.1.10-rc.0
Patch Changes
guide-example@0.0.85-rc.0
Patch Changes
ms-teams-connect-example@0.0.72-rc.0
Patch Changes
nextjs-app-dir-example@0.0.71-rc.0
Patch Changes
nextjs-example@1.2.37-rc.0
Patch Changes
slack-connect-example@0.3.71-rc.0
Patch Changes
slack-kit-example@0.4.69-rc.0
Patch Changes