chore: bump @clerk/react from 6.10.4 to 6.12.0

[dependabot]

Bumps @clerk/react from 6.10.4 to 6.12.0.

Release notes

Sourced from @​clerk/react's releases.

@​clerk/react@​6.12.0

Minor Changes

• Add support for Clerk Protect mid-flow SDK challenges (protect_check) on both sign-up and sign-in. (#8329) by @​zourzouvillys

  When the Protect antifraud service issues a challenge, responses now carry a protectCheck field with { status, token, sdkUrl, expiresAt?, uiHints? }. Clients resolve the gate by loading the SDK at sdkUrl, executing the challenge, and submitting the resulting proof token via signUp.submitProtectCheck({ proofToken }) or signIn.submitProtectCheck({ proofToken }). The response may carry a chained challenge, which the SDK resolves iteratively.

  Sign-in adds a new 'needs_protect_check' value to the SignInStatus union. Upgrading this package is type-only and does not change runtime behavior: the server returns the new status (and the protectCheck field) only for instances where Protect mid-flow challenges have been explicitly enabled — the feature is off by default and is not enabled for existing instances by upgrading. The server additionally only emits the new status value to SDK versions that understand it, so older clients never receive an unknown status.

  If an exhaustive switch on signIn.status flags the new value after upgrading, handle it by running the challenge described by protectCheck and submitting the proof via submitProtectCheck(). Clients should treat the protectCheck field as the authoritative gate signal and fall back to the status value for defense in depth.

  The pre-built <SignIn /> and <SignUp /> components handle the gate automatically by routing to a new protect-check route that runs the challenge SDK and resumes the flow on completion.

Patch Changes

• Updated dependencies [6f97ef5, bab1f29, f2d9e4b]:
  • @​clerk/shared@​4.25.0

@​clerk/react@​6.11.4

Patch Changes

• Updated dependencies [1efc7e5, 5028b54, 2e1fec7]:
  • @​clerk/shared@​4.24.0

@​clerk/react@​6.11.3

Patch Changes

• Updated dependencies [4306146, 533f0b1]:
  • @​clerk/shared@​4.23.0

@​clerk/react@​6.11.1

Patch Changes

• Updated dependencies [19ce04a]:
  • @​clerk/shared@​4.22.0

Changelog

Sourced from @​clerk/react's changelog.

6.12.0

Minor Changes

• Add support for Clerk Protect mid-flow SDK challenges (protect_check) on both sign-up and sign-in. (#8329) by @​zourzouvillys

  When the Protect antifraud service issues a challenge, responses now carry a protectCheck field with { status, token, sdkUrl, expiresAt?, uiHints? }. Clients resolve the gate by loading the SDK at sdkUrl, executing the challenge, and submitting the resulting proof token via signUp.submitProtectCheck({ proofToken }) or signIn.submitProtectCheck({ proofToken }). The response may carry a chained challenge, which the SDK resolves iteratively.

  Sign-in adds a new 'needs_protect_check' value to the SignInStatus union. Upgrading this package is type-only and does not change runtime behavior: the server returns the new status (and the protectCheck field) only for instances where Protect mid-flow challenges have been explicitly enabled — the feature is off by default and is not enabled for existing instances by upgrading. The server additionally only emits the new status value to SDK versions that understand it, so older clients never receive an unknown status.

  If an exhaustive switch on signIn.status flags the new value after upgrading, handle it by running the challenge described by protectCheck and submitting the proof via submitProtectCheck(). Clients should treat the protectCheck field as the authoritative gate signal and fall back to the status value for defense in depth.

  The pre-built <SignIn /> and <SignUp /> components handle the gate automatically by routing to a new protect-check route that runs the challenge SDK and resumes the flow on completion.

Patch Changes

• Updated dependencies [6f97ef5, bab1f29, f2d9e4b]:
  • @​clerk/shared@​4.25.0

6.11.4

Patch Changes

• Updated dependencies [1efc7e5, 5028b54, 2e1fec7]:
  • @​clerk/shared@​4.24.0

6.11.3

Patch Changes

• Updated dependencies [4306146, 533f0b1]:
  • @​clerk/shared@​4.23.0

6.11.2

Patch Changes

... (truncated)

Commits

• 0a29667 ci(repo): Version packages (#9091)
• f2d9e4b feat(clerk-js,shared,ui): Add Protect SDK challenge support during sign-up an...
• 485bca5 ci(repo): Version packages (#9062)
• 59d2456 ci(repo): Version packages (#9035)
• 773acc2 ci(repo): Version packages (#9013)
• 37f9e79 chore(react): Update [DEV] minor & patch dependencies (#9023)
• 85b8831 chore(repo): Update testing to v4 (major) (#8443)
• cb76aa2 fix(clerk-js): validate window navigation protocols and honor allowedRedirect...
• 34c653a ci(repo): Version packages (#8993)
• d79852e ci(repo): Version packages (#8939)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
recode-website	Ready	Preview, Comment	Jul 8, 2026 10:37pm

[github-actions]

Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. The estimated time for response is 5–8 hrs.

In the meantime, please provide all necessary screenshots and make sure you run - npm build run , command and provide a screenshot, a video recording, or an image of the update you made below, which helps speed up the review and assignment. If you have questions, reach out to LinkedIn. Your contributions are highly appreciated!😊

Note: I maintain the repo issue every day twice at 8:00 AM IST and 9:00 PM IST. If your PR goes stale for more than one day, you can tag and comment on this same issue by tagging @sanjay-kv.

We are here to help you on this journey of open source. Consistent 20 contributions are eligible for sponsorship 💰

🎁 check our list of amazing people we sponsored so far: GitHub Sponsorship. ✨

📚Your perks for contribution to this community 👇🏻

1. Get free Consultation use code recode50 to get free: Mentorship for free.

2. Get the Ebook for free use code recode at checkout: Data Science cheatsheet for Beginners.

3. Check out this weekly Newsletter: Sanjay's Newsletter.

If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊

[github-actions]

🎉 Your pull request has been successfully merged! 🎉 Thank you for your valuable contribution to our project.

I would be grateful if you can nominate for keeping this opensource project live and running Link to Nominate. Please do star the repo and Keep up the fantastic work! 🚀