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
@clerk/backend@1.2.0
Minor Changes
Patch Changes
456b06849
]:@clerk/clerk-js@5.5.0
Minor Changes
Add support for GoogleOneTap. New APIs listed: (#3392) by @panteliselef
React component
<GoogleOneTap/>
Customize the UX of the prompt
Use the component from with Vanilla JS
Clerk.openGoogleOneTap(props: GoogleOneTapProps)
Clerk.closeGoogleOneTap()
Low level APIs for custom flows
await Clerk.authenticateWithGoogleOneTap({ token: 'xxxx'})
await Clerk.handleGoogleOneTapCallback()
We recommend using this two methods together in order and let Clerk to perform the correct redirections.
In case you want to handle the redirection and session management yourself you can do so like this
Patch Changes
A bug was fixed to not override the existing sign-up state on the OAuth callback. (#3401) by @LauraBeatris
When continuing a sign-up flow with social connections,
@clerk/clerk-js
was creating a newSignUpResource
object, instead of patching the existing one.This was affecting Web3 sign-up flows, since the wallet ID was being overridden on the browser redirect.
Updated dependencies [
d6a9b3f5d
,456b06849
]:@clerk/nextjs@5.1.0
Minor Changes
Add support for GoogleOneTap. New APIs listed: (#3392) by @panteliselef
React component
<GoogleOneTap/>
Customize the UX of the prompt
Use the component from with Vanilla JS
Clerk.openGoogleOneTap(props: GoogleOneTapProps)
Clerk.closeGoogleOneTap()
Low level APIs for custom flows
await Clerk.authenticateWithGoogleOneTap({ token: 'xxxx'})
await Clerk.handleGoogleOneTapCallback()
We recommend using this two methods together in order and let Clerk to perform the correct redirections.
In case you want to handle the redirection and session management yourself you can do so like this
Patch Changes
d6a9b3f5d
,456b06849
,6888594cc
]:@clerk/clerk-react@5.2.0
Minor Changes
Add support for GoogleOneTap. New APIs listed: (#3392) by @panteliselef
React component
<GoogleOneTap/>
Customize the UX of the prompt
Use the component from with Vanilla JS
Clerk.openGoogleOneTap(props: GoogleOneTapProps)
Clerk.closeGoogleOneTap()
Low level APIs for custom flows
await Clerk.authenticateWithGoogleOneTap({ token: 'xxxx'})
await Clerk.handleGoogleOneTapCallback()
We recommend using this two methods together in order and let Clerk to perform the correct redirections.
In case you want to handle the redirection and session management yourself you can do so like this
Patch Changes
d6a9b3f5d
,456b06849
]:@clerk/shared@2.2.0
Minor Changes
@clerk/types@4.5.0
Minor Changes
Add support for GoogleOneTap. New APIs listed: (#3392) by @panteliselef
React component
<GoogleOneTap/>
Customize the UX of the prompt
Use the component from with Vanilla JS
Clerk.openGoogleOneTap(props: GoogleOneTapProps)
Clerk.closeGoogleOneTap()
Low level APIs for custom flows
await Clerk.authenticateWithGoogleOneTap({ token: 'xxxx'})
await Clerk.handleGoogleOneTapCallback()
We recommend using this two methods together in order and let Clerk to perform the correct redirections.
In case you want to handle the redirection and session management yourself you can do so like this
@clerk/chrome-extension@1.0.13
Patch Changes
62f8af286
,d6a9b3f5d
,456b06849
]:@clerk/clerk-expo@1.1.5
Patch Changes
62f8af286
,d6a9b3f5d
,456b06849
]:@clerk/express@0.0.9
Patch Changes
456b06849
,6888594cc
]:@clerk/fastify@1.0.10
Patch Changes
d6a9b3f5d
,456b06849
,6888594cc
]:@clerk/remix@4.0.11
Patch Changes
d6a9b3f5d
,456b06849
,6888594cc
]:@clerk/clerk-sdk-node@5.0.8
Patch Changes
456b06849
,6888594cc
]:@clerk/testing@1.1.3
Patch Changes
Add experimental console warning on Cypress setup function (#3395) by @anagstef
Updated dependencies [
d6a9b3f5d
,456b06849
]:@clerk/themes@2.1.7
Patch Changes
d6a9b3f5d
]:@clerk/elements@0.4.6