build(deps): bump @clerk/backend from 3.5.0 to 3.7.1 in /dashboard

[dependabot]

Bumps @clerk/backend from 3.5.0 to 3.7.1.

Release notes

Sourced from @​clerk/backend's releases.

@​clerk/backend@​3.7.1

Patch Changes

• Updated dependencies [f4167ec, 17e4164, ed2cf75, 67c04a4, 51c8fdc, c2ba971, 8744728, d9b5c7d]:
  • @​clerk/shared@​4.18.0

@​clerk/backend@​3.7.0

Minor Changes

• Add clerkClient.organizations.replaceOrganizationMetadata(organizationId, params) for replacing an organization's metadata fields in full. (#8787) by @​brunol95

  Use replaceOrganizationMetadata when the provided metadata should become the complete value for that metadata field:

  await clerkClient.organizations.replaceOrganizationMetadata(organizationId, {
    publicMetadata: { plan: 'pro' },
  });

  Use clerkClient.organizations.updateOrganizationMetadata(organizationId, params) when you want to partially update metadata with deep-merge semantics:

  await clerkClient.organizations.updateOrganizationMetadata(organizationId, {
    publicMetadata: { onboardingComplete: true },
  });

  The publicMetadata and privateMetadata parameters on clerkClient.organizations.updateOrganization() are now deprecated. They continue to work, but new code should use updateOrganizationMetadata() for partial updates or replaceOrganizationMetadata() for full replacement.

• Add clerkClient.users.replaceUserMetadata(userId, params) for replacing a user's metadata fields in full. (#8587) by @​brunol95

  Use replaceUserMetadata when the provided metadata should become the complete value for that metadata field:

  await clerkClient.users.replaceUserMetadata(userId, {
    publicMetadata: { plan: 'pro' },
  });

  Use clerkClient.users.updateUserMetadata(userId, params) when you want to partially update metadata with deep-merge semantics:

  await clerkClient.users.updateUserMetadata(userId, {
    publicMetadata: { onboardingComplete: true },
  });

  The publicMetadata, privateMetadata, and unsafeMetadata parameters on clerkClient.users.updateUser() are now deprecated. They continue to work, but new code should use updateUserMetadata() for partial updates or replaceUserMetadata() for full replacement.

Patch Changes

... (truncated)

Changelog

Sourced from @​clerk/backend's changelog.

3.7.1

Patch Changes

• Updated dependencies [f4167ec, 17e4164, ed2cf75, 67c04a4, 51c8fdc, c2ba971, 8744728, d9b5c7d]:
  • @​clerk/shared@​4.18.0

3.7.0

Minor Changes

• Add clerkClient.organizations.replaceOrganizationMetadata(organizationId, params) for replacing an organization's metadata fields in full. (#8787) by @​brunol95

  Use replaceOrganizationMetadata when the provided metadata should become the complete value for that metadata field:

  await clerkClient.organizations.replaceOrganizationMetadata(organizationId, {
    publicMetadata: { plan: 'pro' },
  });

  Use clerkClient.organizations.updateOrganizationMetadata(organizationId, params) when you want to partially update metadata with deep-merge semantics:

  await clerkClient.organizations.updateOrganizationMetadata(organizationId, {
    publicMetadata: { onboardingComplete: true },
  });

  The publicMetadata and privateMetadata parameters on clerkClient.organizations.updateOrganization() are now deprecated. They continue to work, but new code should use updateOrganizationMetadata() for partial updates or replaceOrganizationMetadata() for full replacement.

• Add clerkClient.users.replaceUserMetadata(userId, params) for replacing a user's metadata fields in full. (#8587) by @​brunol95

  Use replaceUserMetadata when the provided metadata should become the complete value for that metadata field:

  await clerkClient.users.replaceUserMetadata(userId, {
    publicMetadata: { plan: 'pro' },
  });

  Use clerkClient.users.updateUserMetadata(userId, params) when you want to partially update metadata with deep-merge semantics:

  await clerkClient.users.updateUserMetadata(userId, {
    publicMetadata: { onboardingComplete: true },
  });

  The publicMetadata, privateMetadata, and unsafeMetadata parameters on clerkClient.users.updateUser() are now deprecated. They continue to work, but new code should use updateUserMetadata() for partial updates or replaceUserMetadata() for full replacement.

... (truncated)

Commits

• 9d7db80 ci(repo): Version packages (#8836)
• 5ebed8b ci(repo): Version packages (#8810)
• b5fa9f6 chore(backend, clerk-js): Deprecate metadata updates in user update methods (...
• cdb940a chore(backend): Deprecate metadata updates in organization update method (#8787)
• f046c49 chore(repo): Upgrade to TypeScript 6.0 (#8177)
• 7cfd510 ci(repo): Version packages (#8803)
• 1028d82 ci(repo): Version packages (#8735)
• e7cb503 fix(backend): correct createOrganizationInvitationBulk return type to Paginat...
• 48b187d fix(backend): return IdPOAuthAccessToken JWT timestamps in milliseconds (#8771)
• 955e998 feat(backend): Add Backend API calls for organization perms, roles (#8774)
• 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)
dashboard-skillcheck	Ready	Preview, Comment	Jun 16, 2026 12:18pm

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.