Skip to content

build(deps): bump @clerk/localizations from 4.16.1 to 4.20.0 - #385

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/bun/clerk/localizations-4.18.0
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/bun/clerk/localizations-4.18.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 27, 2026 •

Copy link
Copy Markdown
Contributor

Bumps @clerk/localizations from 4.16.1 to 4.20.0.

Release notes

Sourced from @​clerk/localizations's releases.

@​clerk/localizations@​4.20.0

Minor Changes

  • <SignIn /> and <SignUp /> show a dedicated screen when a request is blocked, with a reference the user can quote to support. (#9600) by @​zourzouvillys

    action_blocked errors now expose traceId, title, description, linkUrl, linkText, kind and data on meta.

Patch Changes

  • Fix enterprise SSO sign-ins erroring instead of showing a verification challenge raised while handing off to the identity provider. (#9619) by @​zourzouvillys

    If you use the prebuilt <SignIn /> component, there is nothing to do. If you have Clerk Protect enabled and call signIn.authenticateWithRedirect() or signIn.authenticateWithPopup() from a custom sign-in flow, catch a ClerkRuntimeError with code protect_check_required and show the verification challenge, to avoid a stalled sign-in.

    That error means a verification challenge has to be completed before the sign-in can redirect. It replaces the generic "not supported" error these methods threw before. When it is thrown, the sign-in is gated: signIn.protectCheck is set, or its status is needs_protect_check. For enterprise SSO, run the challenge and then call authenticateWithRedirect() again with continueSignIn: true. If the server has already prepared the redirect, the sign-in continues to the identity provider and the challenge runs when it returns, so no error is thrown.

  • Updated dependencies [645a532, 84ee588, 4e538ac]:

    • @​clerk/shared@​4.36.0

@​clerk/localizations@​4.18.0

Minor Changes

  • Rename the SSO fallback sign-in flow to SSO bypass, matching the name the feature ships under. The sign-in resource's ssoFallbackFirstFactors is now ssoBypassFirstFactors and reads the sso_bypass_first_factors field from the API, the signIn.ssoFallback localization keys are now signIn.ssoBypass, and the ssoFallback card action element id is now ssoBypass. The flow has not been enabled on any instance, so no application is affected by the old names going away. (#9822) by @​mauricioabreu

  • Add the ability for Organization admins to manage the SSO bypass allowlist from the Security page of <OrganizationProfile />. (#9809) by @​mauricioabreu

    For custom flows, organization.ssoBypassAllowlist exposes getUsers(), addUser({ userId }) and removeUser(userId).

Patch Changes

  • Each enterprise connection listed on the organization Security page now opens its own page. It lists the connection name and domains, the service provider values to copy into the identity provider, the identity provider configuration behind an Edit form, and the connection settings as a form you save. The header carries one action, either Activate or Continue setup, and deactivating or removing the connection lives in a Danger zone section at the bottom of the page. The row menu is gone; click the row instead. (#9748) by @​NicolasLopes7

    The setup wizard's domains step now shows a checkbox per verified domain, so an admin picks which domains a connection covers. A domain another connection of the organization already authenticates is disabled and labelled with that connection's name, and an error from creating the connection is shown on the provider step instead of being dropped.

    New customization handles ship with it: the organizationProfileSecuritySsoConnectionRow and organizationProfileSecuritySsoConnectionPage appearance elements, the configureSSOVerifyDomainCardCheckbox element, the claimed badge id, the new FieldId values for the connection settings, and the ssoConnectionName, ssoConnectionDomains, ssoConnectionServiceProvider, ssoConnectionIdentityProvider, ssoConnectionSettings and ssoConnectionDangerZone ProfileSectionId values.

  • Updated dependencies [804d3db, 64c8e3e, 07b4c2b, 4e36687, 9e7485c]:

    • @​clerk/shared@​4.34.0
Changelog

Sourced from @​clerk/localizations's changelog.

4.20.0

Minor Changes

  • <SignIn /> and <SignUp /> show a dedicated screen when a request is blocked, with a reference the user can quote to support. (#9600) by @​zourzouvillys

    action_blocked errors now expose traceId, title, description, linkUrl, linkText, kind and data on meta.

Patch Changes

  • Fix enterprise SSO sign-ins erroring instead of showing a verification challenge raised while handing off to the identity provider. (#9619) by @​zourzouvillys

    If you use the prebuilt <SignIn /> component, there is nothing to do. If you have Clerk Protect enabled and call signIn.authenticateWithRedirect() or signIn.authenticateWithPopup() from a custom sign-in flow, catch a ClerkRuntimeError with code protect_check_required and show the verification challenge, to avoid a stalled sign-in.

    That error means a verification challenge has to be completed before the sign-in can redirect. It replaces the generic "not supported" error these methods threw before. When it is thrown, the sign-in is gated: signIn.protectCheck is set, or its status is needs_protect_check. For enterprise SSO, run the challenge and then call authenticateWithRedirect() again with continueSignIn: true. If the server has already prepared the redirect, the sign-in continues to the identity provider and the challenge runs when it returns, so no error is thrown.

  • Updated dependencies [645a532, 84ee588, 4e538ac]:

    • @​clerk/shared@​4.36.0

4.19.0

Minor Changes

  • The "Add members" card on the SSO allow list page of <OrganizationProfile /> now offers two ways to add people: by email address, or every member with a given role at once. Members whose email address is not served by one of the organization's enterprise connections are skipped. When nothing could be added the card stays open and says why, and when some were added it moves to a success step that reports how many were skipped. (#9826) by @​mauricioabreu

    For custom flows, organization.ssoBypassAllowlist gains addUsers({ userIds }), which calls the new bulk endpoint in batches of 100 and returns the added entries together with the users that could not be added and why.

    Inputs marked to be ignored by password managers now also carry the Bitwarden, LastPass and Dashlane opt-out attributes, so those extensions stop offering to fill fields such as the allow list email address.

    The member picker that the "Add member" card shipped with in 4.18.0 is gone, and so are its localization keys under organizationProfile.securityPage.ssoBypassPage.addForm: memberLabel, memberPlaceholder, changeButton and noResults. The feature was never enabled on any instance, so no application depends on them.

    New customization handles: the organizationProfileSecuritySsoBypassEmailInput, organizationProfileSecuritySsoBypassRoleWarning, organizationProfileSecuritySsoBypassFailure and organizationProfileSecuritySsoBypassBulkResult appearance elements.

  • Localize icon-only social sign-in button names using socialButtonsBlockButton and exclude decorative provider icons from the accessibility tree. Add formFieldAction__showPassword and formFieldAction__hidePassword localization keys for password visibility controls, with translations for every supported locale and English fallback for older localization resources. (#9897) by @​jigar-clerk

Patch Changes

4.18.0

Minor Changes

  • Rename the SSO fallback sign-in flow to SSO bypass, matching the name the feature ships under. The sign-in resource's ssoFallbackFirstFactors is now ssoBypassFirstFactors and reads the sso_bypass_first_factors field from the API, the signIn.ssoFallback localization keys are now signIn.ssoBypass, and the ssoFallback card action element id is now ssoBypass. The flow has not been enabled on any instance, so no application is affected by the old names going away. (#9822) by @​mauricioabreu

  • Add the ability for Organization admins to manage the SSO bypass allowlist from the Security page of <OrganizationProfile />. (#9809) by @​mauricioabreu

... (truncated)

Commits
  • 750e7fc ci(repo): Version packages (#9931)
  • 645a532 feat(ui,shared,localizations): dedicated screen for a blocked request (#9600)
  • 84ee588 fix(clerk-js,ui): show the challenge raised while handing off to an enterpris...
  • 8bca915 ci(repo): Version packages (#9893)
  • b3af79e feat(ui): show provider logo on enterprise connection chooser (#9895)
  • d46b544 feat(ui,clerk-js,shared,localizations): Add all members of a role to the SSO ...
  • f50f48c fix(ui,localizations): localize authentication accessible labels (#9897)
  • 0a15af9 ci(repo): Version packages (#9782)
  • 4e36687 feat(ui,clerk-js,shared,localizations): Manage the SSO bypass allowlist from ...
  • 07b4c2b feat(ui,clerk-js,shared,react,localizations): Rename the SSO fallback sign-in...
  • Additional commits viewable in compare view

Summary by CodeRabbit

  • Chores
    • Updated the localization package dependency.

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Sep 27, 2026
@dependabot
dependabot Bot requested a review from bjrump as a code owner September 27, 2026 08:14
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Sep 27, 2026
@vercel

vercel Bot commented Sep 27, 2026 •

Copy link
Copy Markdown
Contributor

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

Project Deployment Actions Updated
car-check Error Error Oct 2, 2026 1:30pm UTC

@coderabbitai

coderabbitai Bot commented Sep 27, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 9243ea37-6895-4de7-87f4-ff7d0436a4d8

📥 Commits

Reviewing files that changed from the base of the PR and between b92afb5 and 37348fd.

⛔ Files ignored due to path filters (1)
  • bun.lock is excluded by !**/*.lock
📒 Files selected for processing (1)
  • package.json

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 1 remain after this review.


📝 Walkthrough

Walkthrough

The declared @clerk/localizations dependency range changes from ^4.16.1 to ^4.20.0.

Changes

Localization Dependency

Layer / File(s) Summary
Update localization dependency range
package.json
The dependency range for @clerk/localizations changes from ^4.16.1 to ^4.20.0.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 37348

The German localization consumer remains supported by the updated package; no merge-blocking issue is established.

Architecture Summary

Architecture risk: 🔵 Low · up to 37348

The change affects 1 system.

Changed systems: package.json

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

  • observed — package.json (service) was modified; 1 changed file maps to changed impact.

Before / after behavior

  • observed — Modified behavior in package.json: Updated the @clerk/localizations dependency range from ^4.16.1 to ^4.20.0.
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the dependency update from @clerk/localizations 4.16.1 to 4.20.0.
✨ Finishing Touches 💡 1
🛠️ Fix failing CI checks 💡
  • Commit to this branch
  • Create a new PR
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.


Comment @coderabbitai help to get the list of available commands.

Bumps [@clerk/localizations](https://github.com/clerk/javascript/tree/HEAD/packages/localizations) from 4.16.1 to 4.20.0.
- [Release notes](https://github.com/clerk/javascript/releases)
- [Changelog](https://github.com/clerk/javascript/blob/main/packages/localizations/CHANGELOG.md)
- [Commits](https://github.com/clerk/javascript/commits/@clerk/localizations@4.20.0/packages/localizations)

---
updated-dependencies:
- dependency-name: "@clerk/localizations"
  dependency-version: 4.18.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title build(deps): bump @clerk/localizations from 4.16.1 to 4.18.0 build(deps): bump @clerk/localizations from 4.16.1 to 4.20.0 Oct 2, 2026
@dependabot
dependabot Bot force-pushed the dependabot/bun/clerk/localizations-4.18.0 branch from 32ab475 to 37348fd Compare October 2, 2026 13:24
@dependabot @github

dependabot Bot commented on behalf of github Oct 4, 2026

Copy link
Copy Markdown
Contributor Author

Superseded by #394.

@dependabot dependabot Bot closed this Oct 4, 2026
@dependabot
dependabot Bot deleted the dependabot/bun/clerk/localizations-4.18.0 branch October 4, 2026 08:13

This branch had an error being deployed

1 failed deployment
Preview — 37348fdf Deployed Oct 2, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants