@clerk/nextjs 7.9.5 patch release
Fixed a React key warning in ClerkProvider with App Router and resolved a cross-request credential leak in clerkMiddleware when using dynamic secret keys. Each request now has its own isolated store to prevent secret key visibility across concurrent requests.
Patch Changes
-
Fix a development-only React key warning when using
ClerkProviderin the App Router. (#9816) by @joshrowley -
Fix a cross-request credential leak in
clerkMiddleware(). When using dynamic keys (an options callback that resolves a differentsecretKeyper request), aclerkClient()call made inside the middleware handler could be built with another concurrent request's secret key. Each request now gets its own isolated store, so the keys resolved for a request are only ever visible to that request. (#9723) by @dominic-clerk -
Updated dependencies [
804d3db,64c8e3e,f56a14b,07b4c2b,4e36687,917453a,3d6ed25,40f40f2,9e7485c]:- @clerk/shared@4.34.0
- @clerk/react@6.17.0
- @clerk/backend@3.19.0
Source: original entry ↗
More from Clerk
Follow Clerk to get its new changes in your feed and email digest.
@clerk/expo-native-components package introduced
A new @clerk/expo-native-components package is now required for native components (AuthView, UserButton, UserProfileView). Install it before deploying over-the-air updates as errors occur at runtime; import native components from @clerk/expo/native-components and deprecate the old @clerk/expo/native import path.
@clerk/expo-native-components 0.1.0
Introduces @clerk/expo-native-components, a new required package for native components (AuthView, UserButton, UserProfileView). Import native components from @clerk/expo/native-components instead of the deprecated @clerk/expo/native, and install the new package before shipping over-the-air updates to avoid runtime errors.
@clerk/ui@1.40.1
Release of @clerk/ui version 1.40.1 with updates and improvements to the UI component library.