chore(deps): bump @clerk/shared from 3.23.0 to 3.47.5

[dependabot]

Bumps @clerk/shared from 3.23.0 to 3.47.5.

Release notes

Sourced from @​clerk/shared's releases.

@​clerk/shared@​3.47.4

Patch Changes

• Normalize URL paths in createPathMatcher to prevent route protection bypass (#8310) by @​nikosdouvlis

Changelog

Sourced from @​clerk/shared's changelog.

Change Log

4.8.6

Patch Changes

• Auto-proxy FAPI requests for .vercel.app subdomains. When deployed to a .vercel.app domain without explicit proxy or domain configuration, the SDK automatically routes Frontend API requests through /__clerk on the app's own origin. This enables Clerk production mode on Vercel deployments without manual proxy setup. (#8035) by @​brkalow

• Loosen @tanstack/query-core dependency from an exact pin to a caret range (^5.90.16) so it can dedupe with consumer-installed @tanstack/react-query versions. This avoids Vite resolve.dedupe resolution failures under Bun when two divergent copies of query-core end up nested instead of hoisted. (#8417) by @​jacekradko

4.8.5

Patch Changes

• Generate publishable keys with unpadded Base64 encoding to match backend output. (#8400) by @​thiskevinwang

4.8.4

Patch Changes

• Add publishableKeyFromHost utility for resolving the correct publishable key per hostname in multi-domain setups. Re-exported from @clerk/react/internal. (#8398) by @​wobsoriano

• Fix useOrganizationList and useOrganization briefly reporting paginated resources as isLoading: false with empty data before the query starts. (#8395) by @​jacekradko

4.8.3

Patch Changes

• Fix an authorization bypass in has(), auth.protect(), and related predicates when a single call combined conditions from more than one dimension (for example, { permission, reverification } or { feature, permission }). A dimension that should have denied the request was treated as indeterminate and ignored by the combining logic, allowing other passing dimensions to carry the result and authorize the call when it should have failed closed. (#8372) by @​nikosdouvlis

  Behavior is now:

  • When a requested dimension cannot be satisfied because the underlying session data is missing, malformed, or invalid, the call denies. Previously these cases were treated as indeterminate and ignored, which could let another passing dimension carry the call.
  • Fixed a minor bug where session.checkAuthorization() was building authorization options from the membership row id instead of the organization id.

  Single-condition role, permission, feature, and plan checks (has({ permission }), etc.) are unchanged. Single-condition reverification checks are unchanged on well-formed session data; calls with a missing or malformed factorVerificationAge payload now deny where they previously returned indeterminate. Callback-form auth.protect(has => ...) is unaffected unless the callback itself invokes the affected shapes.

  Separately, auth.protect() in @clerk/nextjs previously discarded authorization params (role, permission, feature, plan, reverification) whenever the same argument object also contained unauthenticatedUrl, unauthorizedUrl, or token. TypeScript's excess-property check caught this for inline object literals but did not apply once the argument was assigned to a variable, spread, or used from JavaScript. Mixed-shape calls like auth.protect({ role: 'org:admin', unauthorizedUrl: '/denied' }) or auth.protect({ permission: 'org:X', token: 'session_token' }) now correctly enforce the authorization check instead of silently letting every authenticated caller through.

4.8.2

Patch Changes

• Add emailAddress, phoneNumber, and username support to signUp.update() (#8320) by @​dstaley

• Added development runtime error when mounting <OAuthconsent /> without active session. (#8335) by @​wobsoriano

4.8.1

Patch Changes

... (truncated)

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​clerk/shared since your current version.

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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[github-actions]

MCP Security Check

PASSED - No critical vulnerabilities

MCP Vulnerability Summary

Severity	Count	Status
CRITICAL	0	Pass
HIGH	28	Warning
MEDIUM	0	Info

---

MCP project has strict security requirements. Critical vulnerabilities block merge.