build(deps): bump @clerk/localizations from 4.6.4 to 4.13.2

[dependabot]

Bumps @clerk/localizations from 4.6.4 to 4.13.2.

Release notes

Sourced from @​clerk/localizations's releases.

@​clerk/localizations@​4.13.2

Patch Changes

• Add a clear button to search inputs for quickly resetting the current query. It appears in the <APIKeys /> search and the <OrganizationProfile /> members search. (#9098) by @​alexcarpenter

  Search inputs now expose a shared searchInput appearance element (layered alongside any existing component-specific element), and the clear button is themeable via the new shared searchInputClearButton element. The clear button's label can be customized with the new shared searchInput.action__clear localization key.

• Updated dependencies [8dbf343]:

  • @​clerk/shared@​4.25.2

@​clerk/localizations@​4.13.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/localizations@​4.12.1

Patch Changes

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

@​clerk/localizations@​4.12.0

Minor Changes

... (truncated)

Changelog

Sourced from @​clerk/localizations's changelog.

4.13.2

Patch Changes

• Add a clear button to search inputs for quickly resetting the current query. It appears in the <APIKeys /> search and the <OrganizationProfile /> members search. (#9098) by @​alexcarpenter

  Search inputs now expose a shared searchInput appearance element (layered alongside any existing component-specific element), and the clear button is themeable via the new shared searchInputClearButton element. The clear button's label can be customized with the new shared searchInput.action__clear localization key.

• Updated dependencies [8dbf343]:

  • @​clerk/shared@​4.25.2

4.13.1

Patch Changes

• Updated dependencies [62f6702]:
  • @​clerk/shared@​4.25.1

4.13.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

... (truncated)

Commits

• 3fc812f ci(repo): Version packages (#9117)
• 8dbf343 feat(ui): Add clear button to search inputs (#9098)
• 39f190b ci(repo): Version packages (#9108)
• 0a29667 ci(repo): Version packages (#9091)
• 7516127 chore(localizations): Align all locales with en-US and make generate resilien...
• 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)
• 4306146 feat(clerk-js, localizations, ui): Add credits information in the user/org pr...
• 773acc2 ci(repo): Version packages (#9013)
• 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)
car-check	Error		Jul 12, 2026 8:15am