build(deps-dev): bump @clerk/shared from 4.29.1 to 4.30.1

[dependabot]

Bumps @clerk/shared from 4.29.1 to 4.30.1.

Release notes

Sourced from @​clerk/shared's releases.

@​clerk/shared@​4.30.1

Patch Changes

• Fix an issue where a verification that was still progressing normally could be cancelled and reported to the user as having timed out. (#9527) by @​zourzouvillys

@​clerk/shared@​4.30.0

Minor Changes

• Fixes an issue where OAuth account transfers that needed additional verification were returned to the beginning of sign-in. (#9497) by @​zourzouvillys

Patch Changes

• Keep Clerk's navigation inside the renderer. ClerkProvider now always supplies routerPush/routerReplace, so Clerk routes through your application's router when you provide one, and never navigates the window to an internal /CLERK-ROUTER/VIRTUAL/... path — which no custom protocol handler can serve, and which reloaded the renderer and dropped the user out of sign-in. (#9530) by @​jeremy-clerk

  Applications that worked around this by passing no-op router functions, or by filtering CLERK-ROUTER/VIRTUAL out themselves, can remove those workarounds.

• Polish the missing/invalid key error copy: drop the two-space indent before the npx clerk@latest init command (it rendered as a stray space in browser error overlays), start the follow-up sentence with the command name instead of "It" so the sentence stands on its own, and reword "Requires no Clerk account or login" to "No Clerk account or login required". (#9531) by @​eatmorespinach

• Fix an issue where sign-ups that used an enterprise SSO connection did not correctly forward redirect URLs. (#9449) by @​zourzouvillys

@​clerk/shared@​4.29.3

Patch Changes

• Update missing and invalid key error messages to recommend the Clerk CLI: npx clerk@latest init (non-interactive, no Clerk account required) to create an application, npx clerk@latest env pull to fetch the keys of an existing one, and npx clerk@latest deploy / npx clerk@latest env pull --instance prod for production. This covers both the errorThrower messages and the errors thrown by parsePublishableKey(key, { fatal: true }), which previously surfaced server-side as a bare Publishable key not valid. The Dashboard link is kept for manual key copying. (#9491) by @​djgould

@​clerk/shared@​4.29.2

Patch Changes

• Display a proper message when a password is rejected for matching one of the account's identifiers. Previously this error rendered as the incomplete sentence "Your password must contain ." on sign-up, reset password, and the user profile password form. The new message is available under the unstable__errors.form_password_matches_identifier localization key, and any password error the UI does not recognize now falls back to the message returned by the API instead of an empty sentence. (#9453) by @​dmoerner

Changelog

Sourced from @​clerk/shared's changelog.

4.30.1

Patch Changes

• Fix an issue where a verification that was still progressing normally could be cancelled and reported to the user as having timed out. (#9527) by @​zourzouvillys

4.30.0

Minor Changes

• Fixes an issue where OAuth account transfers that needed additional verification were returned to the beginning of sign-in. (#9497) by @​zourzouvillys

Patch Changes

• Keep Clerk's navigation inside the renderer. ClerkProvider now always supplies routerPush/routerReplace, so Clerk routes through your application's router when you provide one, and never navigates the window to an internal /CLERK-ROUTER/VIRTUAL/... path — which no custom protocol handler can serve, and which reloaded the renderer and dropped the user out of sign-in. (#9530) by @​jeremy-clerk

  Applications that worked around this by passing no-op router functions, or by filtering CLERK-ROUTER/VIRTUAL out themselves, can remove those workarounds.

• Polish the missing/invalid key error copy: drop the two-space indent before the npx clerk@latest init command (it rendered as a stray space in browser error overlays), start the follow-up sentence with the command name instead of "It" so the sentence stands on its own, and reword "Requires no Clerk account or login" to "No Clerk account or login required". (#9531) by @​eatmorespinach

• Fix an issue where sign-ups that used an enterprise SSO connection did not correctly forward redirect URLs. (#9449) by @​zourzouvillys

4.29.3

Patch Changes

• Update missing and invalid key error messages to recommend the Clerk CLI: npx clerk@latest init (non-interactive, no Clerk account required) to create an application, npx clerk@latest env pull to fetch the keys of an existing one, and npx clerk@latest deploy / npx clerk@latest env pull --instance prod for production. This covers both the errorThrower messages and the errors thrown by parsePublishableKey(key, { fatal: true }), which previously surfaced server-side as a bare Publishable key not valid. The Dashboard link is kept for manual key copying. (#9491) by @​djgould

4.29.2

Patch Changes

• Display a proper message when a password is rejected for matching one of the account's identifiers. Previously this error rendered as the incomplete sentence "Your password must contain ." on sign-up, reset password, and the user profile password form. The new message is available under the unstable__errors.form_password_matches_identifier localization key, and any password error the UI does not recognize now falls back to the message returned by the API instead of an empty sentence. (#9453) by @​dmoerner

Commits

• 2799f0d ci(repo): Version packages (#9538)
• dbaa95a fix(clerk-js,react,shared,ui): bound loading a verification, not running one ...
• 27dbf26 ci(repo): Version packages (#9521)
• 28b77ac fix(electron,shared,ui): keep Clerk navigation inside the Electron renderer (...
• 46bf7ce feat(shared): polish missing/invalid key error copy (#9531)
• e21ae9a docs(shared,ui): address the review comments from #9449 (#9522)
• 8bc1c9f fix(clerk-js,react,shared,ui): resume an OAuth transfer after a verification ...
• 17b865b fix(ui): populate enterprise SSO redirect urls when continuing a sign-up (#9449)
• 297c03d ci(repo): Version packages (#9514)
• ea8cb05 feat(shared): point missing and invalid key errors at the Clerk CLI (#9491)
• Additional commits viewable in compare view

[changeset-bot]

⚠️ No Changeset found

Latest commit: e815ae8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[dependabot]

Bumps @clerk/shared from 4.29.1 to 4.30.1.

Release notes

Sourced from @​clerk/shared's releases.

@​clerk/shared@​4.30.1

Patch Changes

• Fix an issue where a verification that was still progressing normally could be cancelled and reported to the user as having timed out. (#9527) by @​zourzouvillys

@​clerk/shared@​4.30.0

Minor Changes

• Fixes an issue where OAuth account transfers that needed additional verification were returned to the beginning of sign-in. (#9497) by @​zourzouvillys

Patch Changes

• Keep Clerk's navigation inside the renderer. ClerkProvider now always supplies routerPush/routerReplace, so Clerk routes through your application's router when you provide one, and never navigates the window to an internal /CLERK-ROUTER/VIRTUAL/... path — which no custom protocol handler can serve, and which reloaded the renderer and dropped the user out of sign-in. (#9530) by @​jeremy-clerk

  Applications that worked around this by passing no-op router functions, or by filtering CLERK-ROUTER/VIRTUAL out themselves, can remove those workarounds.

• Polish the missing/invalid key error copy: drop the two-space indent before the npx clerk@latest init command (it rendered as a stray space in browser error overlays), start the follow-up sentence with the command name instead of "It" so the sentence stands on its own, and reword "Requires no Clerk account or login" to "No Clerk account or login required". (#9531) by @​eatmorespinach

• Fix an issue where sign-ups that used an enterprise SSO connection did not correctly forward redirect URLs. (#9449) by @​zourzouvillys

@​clerk/shared@​4.29.3

Patch Changes

• Update missing and invalid key error messages to recommend the Clerk CLI: npx clerk@latest init (non-interactive, no Clerk account required) to create an application, npx clerk@latest env pull to fetch the keys of an existing one, and npx clerk@latest deploy / npx clerk@latest env pull --instance prod for production. This covers both the errorThrower messages and the errors thrown by parsePublishableKey(key, { fatal: true }), which previously surfaced server-side as a bare Publishable key not valid. The Dashboard link is kept for manual key copying. (#9491) by @​djgould

@​clerk/shared@​4.29.2

Patch Changes

• Display a proper message when a password is rejected for matching one of the account's identifiers. Previously this error rendered as the incomplete sentence "Your password must contain ." on sign-up, reset password, and the user profile password form. The new message is available under the unstable__errors.form_password_matches_identifier localization key, and any password error the UI does not recognize now falls back to the message returned by the API instead of an empty sentence. (#9453) by @​dmoerner

Changelog

Sourced from @​clerk/shared's changelog.

4.30.1

Patch Changes

• Fix an issue where a verification that was still progressing normally could be cancelled and reported to the user as having timed out. (#9527) by @​zourzouvillys

4.30.0

Minor Changes

• Fixes an issue where OAuth account transfers that needed additional verification were returned to the beginning of sign-in. (#9497) by @​zourzouvillys

Patch Changes

• Keep Clerk's navigation inside the renderer. ClerkProvider now always supplies routerPush/routerReplace, so Clerk routes through your application's router when you provide one, and never navigates the window to an internal /CLERK-ROUTER/VIRTUAL/... path — which no custom protocol handler can serve, and which reloaded the renderer and dropped the user out of sign-in. (#9530) by @​jeremy-clerk

  Applications that worked around this by passing no-op router functions, or by filtering CLERK-ROUTER/VIRTUAL out themselves, can remove those workarounds.

• Polish the missing/invalid key error copy: drop the two-space indent before the npx clerk@latest init command (it rendered as a stray space in browser error overlays), start the follow-up sentence with the command name instead of "It" so the sentence stands on its own, and reword "Requires no Clerk account or login" to "No Clerk account or login required". (#9531) by @​eatmorespinach

• Fix an issue where sign-ups that used an enterprise SSO connection did not correctly forward redirect URLs. (#9449) by @​zourzouvillys

4.29.3

Patch Changes

• Update missing and invalid key error messages to recommend the Clerk CLI: npx clerk@latest init (non-interactive, no Clerk account required) to create an application, npx clerk@latest env pull to fetch the keys of an existing one, and npx clerk@latest deploy / npx clerk@latest env pull --instance prod for production. This covers both the errorThrower messages and the errors thrown by parsePublishableKey(key, { fatal: true }), which previously surfaced server-side as a bare Publishable key not valid. The Dashboard link is kept for manual key copying. (#9491) by @​djgould

4.29.2

Patch Changes

• Display a proper message when a password is rejected for matching one of the account's identifiers. Previously this error rendered as the incomplete sentence "Your password must contain ." on sign-up, reset password, and the user profile password form. The new message is available under the unstable__errors.form_password_matches_identifier localization key, and any password error the UI does not recognize now falls back to the message returned by the API instead of an empty sentence. (#9453) by @​dmoerner

Commits

• 2799f0d ci(repo): Version packages (#9538)
• dbaa95a fix(clerk-js,react,shared,ui): bound loading a verification, not running one ...
• 27dbf26 ci(repo): Version packages (#9521)
• 28b77ac fix(electron,shared,ui): keep Clerk navigation inside the Electron renderer (...
• 46bf7ce feat(shared): polish missing/invalid key error copy (#9531)
• e21ae9a docs(shared,ui): address the review comments from #9449 (#9522)
• 8bc1c9f fix(clerk-js,react,shared,ui): resume an OAuth transfer after a verification ...
• 17b865b fix(ui): populate enterprise SSO redirect urls when continuing a sign-up (#9449)
• 297c03d ci(repo): Version packages (#9514)
• ea8cb05 feat(shared): point missing and invalid key errors at the Clerk CLI (#9491)
• Additional commits viewable in compare view

[changeset-bot]

⚠️ No Changeset found

Latest commit: e815ae8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[dependabot]

Bumps @clerk/shared from 4.29.1 to 4.30.1.

Release notes

Sourced from @​clerk/shared's releases.

@​clerk/shared@​4.30.1

Patch Changes

• Fix an issue where a verification that was still progressing normally could be cancelled and reported to the user as having timed out. (#9527) by @​zourzouvillys

@​clerk/shared@​4.30.0

Minor Changes

• Fixes an issue where OAuth account transfers that needed additional verification were returned to the beginning of sign-in. (#9497) by @​zourzouvillys

Patch Changes

• Keep Clerk's navigation inside the renderer. ClerkProvider now always supplies routerPush/routerReplace, so Clerk routes through your application's router when you provide one, and never navigates the window to an internal /CLERK-ROUTER/VIRTUAL/... path — which no custom protocol handler can serve, and which reloaded the renderer and dropped the user out of sign-in. (#9530) by @​jeremy-clerk

  Applications that worked around this by passing no-op router functions, or by filtering CLERK-ROUTER/VIRTUAL out themselves, can remove those workarounds.

• Polish the missing/invalid key error copy: drop the two-space indent before the npx clerk@latest init command (it rendered as a stray space in browser error overlays), start the follow-up sentence with the command name instead of "It" so the sentence stands on its own, and reword "Requires no Clerk account or login" to "No Clerk account or login required". (#9531) by @​eatmorespinach

• Fix an issue where sign-ups that used an enterprise SSO connection did not correctly forward redirect URLs. (#9449) by @​zourzouvillys

@​clerk/shared@​4.29.3

Patch Changes

• Update missing and invalid key error messages to recommend the Clerk CLI: npx clerk@latest init (non-interactive, no Clerk account required) to create an application, npx clerk@latest env pull to fetch the keys of an existing one, and npx clerk@latest deploy / npx clerk@latest env pull --instance prod for production. This covers both the errorThrower messages and the errors thrown by parsePublishableKey(key, { fatal: true }), which previously surfaced server-side as a bare Publishable key not valid. The Dashboard link is kept for manual key copying. (#9491) by @​djgould

@​clerk/shared@​4.29.2

Patch Changes

• Display a proper message when a password is rejected for matching one of the account's identifiers. Previously this error rendered as the incomplete sentence "Your password must contain ." on sign-up, reset password, and the user profile password form. The new message is available under the unstable__errors.form_password_matches_identifier localization key, and any password error the UI does not recognize now falls back to the message returned by the API instead of an empty sentence. (#9453) by @​dmoerner

Changelog

Sourced from @​clerk/shared's changelog.

4.30.1

Patch Changes

• Fix an issue where a verification that was still progressing normally could be cancelled and reported to the user as having timed out. (#9527) by @​zourzouvillys

4.30.0

Minor Changes

• Fixes an issue where OAuth account transfers that needed additional verification were returned to the beginning of sign-in. (#9497) by @​zourzouvillys

Patch Changes

• Keep Clerk's navigation inside the renderer. ClerkProvider now always supplies routerPush/routerReplace, so Clerk routes through your application's router when you provide one, and never navigates the window to an internal /CLERK-ROUTER/VIRTUAL/... path — which no custom protocol handler can serve, and which reloaded the renderer and dropped the user out of sign-in. (#9530) by @​jeremy-clerk

  Applications that worked around this by passing no-op router functions, or by filtering CLERK-ROUTER/VIRTUAL out themselves, can remove those workarounds.

• Polish the missing/invalid key error copy: drop the two-space indent before the npx clerk@latest init command (it rendered as a stray space in browser error overlays), start the follow-up sentence with the command name instead of "It" so the sentence stands on its own, and reword "Requires no Clerk account or login" to "No Clerk account or login required". (#9531) by @​eatmorespinach

• Fix an issue where sign-ups that used an enterprise SSO connection did not correctly forward redirect URLs. (#9449) by @​zourzouvillys

4.29.3

Patch Changes

• Update missing and invalid key error messages to recommend the Clerk CLI: npx clerk@latest init (non-interactive, no Clerk account required) to create an application, npx clerk@latest env pull to fetch the keys of an existing one, and npx clerk@latest deploy / npx clerk@latest env pull --instance prod for production. This covers both the errorThrower messages and the errors thrown by parsePublishableKey(key, { fatal: true }), which previously surfaced server-side as a bare Publishable key not valid. The Dashboard link is kept for manual key copying. (#9491) by @​djgould

4.29.2

Patch Changes

• Display a proper message when a password is rejected for matching one of the account's identifiers. Previously this error rendered as the incomplete sentence "Your password must contain ." on sign-up, reset password, and the user profile password form. The new message is available under the unstable__errors.form_password_matches_identifier localization key, and any password error the UI does not recognize now falls back to the message returned by the API instead of an empty sentence. (#9453) by @​dmoerner

Commits

• 2799f0d ci(repo): Version packages (#9538)
• dbaa95a fix(clerk-js,react,shared,ui): bound loading a verification, not running one ...
• 27dbf26 ci(repo): Version packages (#9521)
• 28b77ac fix(electron,shared,ui): keep Clerk navigation inside the Electron renderer (...
• 46bf7ce feat(shared): polish missing/invalid key error copy (#9531)
• e21ae9a docs(shared,ui): address the review comments from #9449 (#9522)
• 8bc1c9f fix(clerk-js,react,shared,ui): resume an OAuth transfer after a verification ...
• 17b865b fix(ui): populate enterprise SSO redirect urls when continuing a sign-up (#9449)
• 297c03d ci(repo): Version packages (#9514)
• ea8cb05 feat(shared): point missing and invalid key errors at the Clerk CLI (#9491)
• Additional commits viewable in compare view

[changeset-bot]

⚠️ No Changeset found

Latest commit: e815ae8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[dependabot]

Bumps @clerk/shared from 4.29.1 to 4.30.1.

Release notes

Sourced from @​clerk/shared's releases.

@​clerk/shared@​4.30.1

Patch Changes

• Fix an issue where a verification that was still progressing normally could be cancelled and reported to the user as having timed out. (#9527) by @​zourzouvillys

@​clerk/shared@​4.30.0

Minor Changes

• Fixes an issue where OAuth account transfers that needed additional verification were returned to the beginning of sign-in. (#9497) by @​zourzouvillys

Patch Changes

• Keep Clerk's navigation inside the renderer. ClerkProvider now always supplies routerPush/routerReplace, so Clerk routes through your application's router when you provide one, and never navigates the window to an internal /CLERK-ROUTER/VIRTUAL/... path — which no custom protocol handler can serve, and which reloaded the renderer and dropped the user out of sign-in. (#9530) by @​jeremy-clerk

  Applications that worked around this by passing no-op router functions, or by filtering CLERK-ROUTER/VIRTUAL out themselves, can remove those workarounds.

• Polish the missing/invalid key error copy: drop the two-space indent before the npx clerk@latest init command (it rendered as a stray space in browser error overlays), start the follow-up sentence with the command name instead of "It" so the sentence stands on its own, and reword "Requires no Clerk account or login" to "No Clerk account or login required". (#9531) by @​eatmorespinach

• Fix an issue where sign-ups that used an enterprise SSO connection did not correctly forward redirect URLs. (#9449) by @​zourzouvillys

@​clerk/shared@​4.29.3

Patch Changes

• Update missing and invalid key error messages to recommend the Clerk CLI: npx clerk@latest init (non-interactive, no Clerk account required) to create an application, npx clerk@latest env pull to fetch the keys of an existing one, and npx clerk@latest deploy / npx clerk@latest env pull --instance prod for production. This covers both the errorThrower messages and the errors thrown by parsePublishableKey(key, { fatal: true }), which previously surfaced server-side as a bare Publishable key not valid. The Dashboard link is kept for manual key copying. (#9491) by @​djgould

@​clerk/shared@​4.29.2

Patch Changes

• Display a proper message when a password is rejected for matching one of the account's identifiers. Previously this error rendered as the incomplete sentence "Your password must contain ." on sign-up, reset password, and the user profile password form. The new message is available under the unstable__errors.form_password_matches_identifier localization key, and any password error the UI does not recognize now falls back to the message returned by the API instead of an empty sentence. (#9453) by @​dmoerner

Changelog

Sourced from @​clerk/shared's changelog.

4.30.1

Patch Changes

• Fix an issue where a verification that was still progressing normally could be cancelled and reported to the user as having timed out. (#9527) by @​zourzouvillys

4.30.0

Minor Changes

• Fixes an issue where OAuth account transfers that needed additional verification were returned to the beginning of sign-in. (#9497) by @​zourzouvillys

Patch Changes

• Keep Clerk's navigation inside the renderer. ClerkProvider now always supplies routerPush/routerReplace, so Clerk routes through your application's router when you provide one, and never navigates the window to an internal /CLERK-ROUTER/VIRTUAL/... path — which no custom protocol handler can serve, and which reloaded the renderer and dropped the user out of sign-in. (#9530) by @​jeremy-clerk

  Applications that worked around this by passing no-op router functions, or by filtering CLERK-ROUTER/VIRTUAL out themselves, can remove those workarounds.

• Polish the missing/invalid key error copy: drop the two-space indent before the npx clerk@latest init command (it rendered as a stray space in browser error overlays), start the follow-up sentence with the command name instead of "It" so the sentence stands on its own, and reword "Requires no Clerk account or login" to "No Clerk account or login required". (#9531) by @​eatmorespinach

• Fix an issue where sign-ups that used an enterprise SSO connection did not correctly forward redirect URLs. (#9449) by @​zourzouvillys

4.29.3

Patch Changes

• Update missing and invalid key error messages to recommend the Clerk CLI: npx clerk@latest init (non-interactive, no Clerk account required) to create an application, npx clerk@latest env pull to fetch the keys of an existing one, and npx clerk@latest deploy / npx clerk@latest env pull --instance prod for production. This covers both the errorThrower messages and the errors thrown by parsePublishableKey(key, { fatal: true }), which previously surfaced server-side as a bare Publishable key not valid. The Dashboard link is kept for manual key copying. (#9491) by @​djgould

4.29.2

Patch Changes

• Display a proper message when a password is rejected for matching one of the account's identifiers. Previously this error rendered as the incomplete sentence "Your password must contain ." on sign-up, reset password, and the user profile password form. The new message is available under the unstable__errors.form_password_matches_identifier localization key, and any password error the UI does not recognize now falls back to the message returned by the API instead of an empty sentence. (#9453) by @​dmoerner

Commits

• 2799f0d ci(repo): Version packages (#9538)
• dbaa95a fix(clerk-js,react,shared,ui): bound loading a verification, not running one ...
• 27dbf26 ci(repo): Version packages (#9521)
• 28b77ac fix(electron,shared,ui): keep Clerk navigation inside the Electron renderer (...
• 46bf7ce feat(shared): polish missing/invalid key error copy (#9531)
• e21ae9a docs(shared,ui): address the review comments from #9449 (#9522)
• 8bc1c9f fix(clerk-js,react,shared,ui): resume an OAuth transfer after a verification ...
• 17b865b fix(ui): populate enterprise SSO redirect urls when continuing a sign-up (#9449)
• 297c03d ci(repo): Version packages (#9514)
• ea8cb05 feat(shared): point missing and invalid key errors at the Clerk CLI (#9491)
• Additional commits viewable in compare view

[changeset-bot]

⚠️ No Changeset found

Latest commit: e815ae8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[dependabot]

Bumps @clerk/shared from 4.29.1 to 4.30.1.

Release notes

Sourced from @​clerk/shared's releases.

@​clerk/shared@​4.30.1

Patch Changes

• Fix an issue where a verification that was still progressing normally could be cancelled and reported to the user as having timed out. (#9527) by @​zourzouvillys

@​clerk/shared@​4.30.0

Minor Changes

• Fixes an issue where OAuth account transfers that needed additional verification were returned to the beginning of sign-in. (#9497) by @​zourzouvillys

Patch Changes

• Keep Clerk's navigation inside the renderer. ClerkProvider now always supplies routerPush/routerReplace, so Clerk routes through your application's router when you provide one, and never navigates the window to an internal /CLERK-ROUTER/VIRTUAL/... path — which no custom protocol handler can serve, and which reloaded the renderer and dropped the user out of sign-in. (#9530) by @​jeremy-clerk

  Applications that worked around this by passing no-op router functions, or by filtering CLERK-ROUTER/VIRTUAL out themselves, can remove those workarounds.

• Polish the missing/invalid key error copy: drop the two-space indent before the npx clerk@latest init command (it rendered as a stray space in browser error overlays), start the follow-up sentence with the command name instead of "It" so the sentence stands on its own, and reword "Requires no Clerk account or login" to "No Clerk account or login required". (#9531) by @​eatmorespinach

• Fix an issue where sign-ups that used an enterprise SSO connection did not correctly forward redirect URLs. (#9449) by @​zourzouvillys

@​clerk/shared@​4.29.3

Patch Changes

• Update missing and invalid key error messages to recommend the Clerk CLI: npx clerk@latest init (non-interactive, no Clerk account required) to create an application, npx clerk@latest env pull to fetch the keys of an existing one, and npx clerk@latest deploy / npx clerk@latest env pull --instance prod for production. This covers both the errorThrower messages and the errors thrown by parsePublishableKey(key, { fatal: true }), which previously surfaced server-side as a bare Publishable key not valid. The Dashboard link is kept for manual key copying. (#9491) by @​djgould

@​clerk/shared@​4.29.2

Patch Changes

• Display a proper message when a password is rejected for matching one of the account's identifiers. Previously this error rendered as the incomplete sentence "Your password must contain ." on sign-up, reset password, and the user profile password form. The new message is available under the unstable__errors.form_password_matches_identifier localization key, and any password error the UI does not recognize now falls back to the message returned by the API instead of an empty sentence. (#9453) by @​dmoerner

Changelog

Sourced from @​clerk/shared's changelog.

4.30.1

Patch Changes

• Fix an issue where a verification that was still progressing normally could be cancelled and reported to the user as having timed out. (#9527) by @​zourzouvillys

4.30.0

Minor Changes

• Fixes an issue where OAuth account transfers that needed additional verification were returned to the beginning of sign-in. (#9497) by @​zourzouvillys

Patch Changes

• Keep Clerk's navigation inside the renderer. ClerkProvider now always supplies routerPush/routerReplace, so Clerk routes through your application's router when you provide one, and never navigates the window to an internal /CLERK-ROUTER/VIRTUAL/... path — which no custom protocol handler can serve, and which reloaded the renderer and dropped the user out of sign-in. (#9530) by @​jeremy-clerk

  Applications that worked around this by passing no-op router functions, or by filtering CLERK-ROUTER/VIRTUAL out themselves, can remove those workarounds.

• Polish the missing/invalid key error copy: drop the two-space indent before the npx clerk@latest init command (it rendered as a stray space in browser error overlays), start the follow-up sentence with the command name instead of "It" so the sentence stands on its own, and reword "Requires no Clerk account or login" to "No Clerk account or login required". (#9531) by @​eatmorespinach

• Fix an issue where sign-ups that used an enterprise SSO connection did not correctly forward redirect URLs. (#9449) by @​zourzouvillys

4.29.3

Patch Changes

• Update missing and invalid key error messages to recommend the Clerk CLI: npx clerk@latest init (non-interactive, no Clerk account required) to create an application, npx clerk@latest env pull to fetch the keys of an existing one, and npx clerk@latest deploy / npx clerk@latest env pull --instance prod for production. This covers both the errorThrower messages and the errors thrown by parsePublishableKey(key, { fatal: true }), which previously surfaced server-side as a bare Publishable key not valid. The Dashboard link is kept for manual key copying. (#9491) by @​djgould

4.29.2

Patch Changes

• Display a proper message when a password is rejected for matching one of the account's identifiers. Previously this error rendered as the incomplete sentence "Your password must contain ." on sign-up, reset password, and the user profile password form. The new message is available under the unstable__errors.form_password_matches_identifier localization key, and any password error the UI does not recognize now falls back to the message returned by the API instead of an empty sentence. (#9453) by @​dmoerner

Commits

• 2799f0d ci(repo): Version packages (#9538)
• dbaa95a fix(clerk-js,react,shared,ui): bound loading a verification, not running one ...
• 27dbf26 ci(repo): Version packages (#9521)
• 28b77ac fix(electron,shared,ui): keep Clerk navigation inside the Electron renderer (...
• 46bf7ce feat(shared): polish missing/invalid key error copy (#9531)
• e21ae9a docs(shared,ui): address the review comments from #9449 (#9522)
• 8bc1c9f fix(clerk-js,react,shared,ui): resume an OAuth transfer after a verification ...
• 17b865b fix(ui): populate enterprise SSO redirect urls when continuing a sign-up (#9449)
• 297c03d ci(repo): Version packages (#9514)
• ea8cb05 feat(shared): point missing and invalid key errors at the Clerk CLI (#9491)
• Additional commits viewable in compare view

[changeset-bot]

⚠️ No Changeset found

Latest commit: e815ae8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[dependabot]

Bumps @clerk/shared from 4.29.1 to 4.30.1.

Release notes

Sourced from @​clerk/shared's releases.

@​clerk/shared@​4.30.1

Patch Changes

• Fix an issue where a verification that was still progressing normally could be cancelled and reported to the user as having timed out. (#9527) by @​zourzouvillys

@​clerk/shared@​4.30.0

Minor Changes

• Fixes an issue where OAuth account transfers that needed additional verification were returned to the beginning of sign-in. (#9497) by @​zourzouvillys

Patch Changes

• Keep Clerk's navigation inside the renderer. ClerkProvider now always supplies routerPush/routerReplace, so Clerk routes through your application's router when you provide one, and never navigates the window to an internal /CLERK-ROUTER/VIRTUAL/... path — which no custom protocol handler can serve, and which reloaded the renderer and dropped the user out of sign-in. (#9530) by @​jeremy-clerk

  Applications that worked around this by passing no-op router functions, or by filtering CLERK-ROUTER/VIRTUAL out themselves, can remove those workarounds.

• Polish the missing/invalid key error copy: drop the two-space indent before the npx clerk@latest init command (it rendered as a stray space in browser error overlays), start the follow-up sentence with the command name instead of "It" so the sentence stands on its own, and reword "Requires no Clerk account or login" to "No Clerk account or login required". (#9531) by @​eatmorespinach

• Fix an issue where sign-ups that used an enterprise SSO connection did not correctly forward redirect URLs. (#9449) by @​zourzouvillys

@​clerk/shared@​4.29.3

Patch Changes

• Update missing and invalid key error messages to recommend the Clerk CLI: npx clerk@latest init (non-interactive, no Clerk account required) to create an application, npx clerk@latest env pull to fetch the keys of an existing one, and npx clerk@latest deploy / npx clerk@latest env pull --instance prod for production. This covers both the errorThrower messages and the errors thrown by parsePublishableKey(key, { fatal: true }), which previously surfaced server-side as a bare Publishable key not valid. The Dashboard link is kept for manual key copying. (#9491) by @​djgould

@​clerk/shared@​4.29.2

Patch Changes

• Display a proper message when a password is rejected for matching one of the account's identifiers. Previously this error rendered as the incomplete sentence "Your password must contain ." on sign-up, reset password, and the user profile password form. The new message is available under the unstable__errors.form_password_matches_identifier localization key, and any password error the UI does not recognize now falls back to the message returned by the API instead of an empty sentence. (#9453) by @​dmoerner

Changelog

Sourced from @​clerk/shared's changelog.

4.30.1

Patch Changes

• Fix an issue where a verification that was still progressing normally could be cancelled and reported to the user as having timed out. (#9527) by @​zourzouvillys

4.30.0

Minor Changes

• Fixes an issue where OAuth account transfers that needed additional verification were returned to the beginning of sign-in. (#9497) by @​zourzouvillys

Patch Changes

• Keep Clerk's navigation inside the renderer. ClerkProvider now always supplies routerPush/routerReplace, so Clerk routes through your application's router when you provide one, and never navigates the window to an internal /CLERK-ROUTER/VIRTUAL/... path — which no custom protocol handler can serve, and which reloaded the renderer and dropped the user out of sign-in. (#9530) by @​jeremy-clerk

  Applications that worked around this by passing no-op router functions, or by filtering CLERK-ROUTER/VIRTUAL out themselves, can remove those workarounds.

• Polish the missing/invalid key error copy: drop the two-space indent before the npx clerk@latest init command (it rendered as a stray space in browser error overlays), start the follow-up sentence with the command name instead of "It" so the sentence stands on its own, and reword "Requires no Clerk account or login" to "No Clerk account or login required". (#9531) by @​eatmorespinach

• Fix an issue where sign-ups that used an enterprise SSO connection did not correctly forward redirect URLs. (#9449) by @​zourzouvillys

4.29.3

Patch Changes

• Update missing and invalid key error messages to recommend the Clerk CLI: npx clerk@latest init (non-interactive, no Clerk account required) to create an application, npx clerk@latest env pull to fetch the keys of an existing one, and npx clerk@latest deploy / npx clerk@latest env pull --instance prod for production. This covers both the errorThrower messages and the errors thrown by parsePublishableKey(key, { fatal: true }), which previously surfaced server-side as a bare Publishable key not valid. The Dashboard link is kept for manual key copying. (#9491) by @​djgould

4.29.2

Patch Changes

• Display a proper message when a password is rejected for matching one of the account's identifiers. Previously this error rendered as the incomplete sentence "Your password must contain ." on sign-up, reset password, and the user profile password form. The new message is available under the unstable__errors.form_password_matches_identifier localization key, and any password error the UI does not recognize now falls back to the message returned by the API instead of an empty sentence. (#9453) by @​dmoerner

Commits

• 2799f0d ci(repo): Version packages (#9538)
• dbaa95a fix(clerk-js,react,shared,ui): bound loading a verification, not running one ...
• 27dbf26 ci(repo): Version packages (#9521)
• 28b77ac fix(electron,shared,ui): keep Clerk navigation inside the Electron renderer (...
• 46bf7ce feat(shared): polish missing/invalid key error copy (#9531)
• e21ae9a docs(shared,ui): address the review comments from #9449 (#9522)
• 8bc1c9f fix(clerk-js,react,shared,ui): resume an OAuth transfer after a verification ...
• 17b865b fix(ui): populate enterprise SSO redirect urls when continuing a sign-up (#9449)
• 297c03d ci(repo): Version packages (#9514)
• ea8cb05 feat(shared): point missing and invalid key errors at the Clerk CLI (#9491)
• Additional commits viewable in compare view

[changeset-bot]

⚠️ No Changeset found

Latest commit: e815ae8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[dependabot]

Bumps @clerk/shared from 4.29.1 to 4.30.1.

Release notes

Sourced from @​clerk/shared's releases.

@​clerk/shared@​4.30.1

Patch Changes

• Fix an issue where a verification that was still progressing normally could be cancelled and reported to the user as having timed out. (#9527) by @​zourzouvillys

@​clerk/shared@​4.30.0

Minor Changes

• Fixes an issue where OAuth account transfers that needed additional verification were returned to the beginning of sign-in. (#9497) by @​zourzouvillys

Patch Changes

• Keep Clerk's navigation inside the renderer. ClerkProvider now always supplies routerPush/routerReplace, so Clerk routes through your application's router when you provide one, and never navigates the window to an internal /CLERK-ROUTER/VIRTUAL/... path — which no custom protocol handler can serve, and which reloaded the renderer and dropped the user out of sign-in. (#9530) by @​jeremy-clerk

  Applications that worked around this by passing no-op router functions, or by filtering CLERK-ROUTER/VIRTUAL out themselves, can remove those workarounds.

• Polish the missing/invalid key error copy: drop the two-space indent before the npx clerk@latest init command (it rendered as a stray space in browser error overlays), start the follow-up sentence with the command name instead of "It" so the sentence stands on its own, and reword "Requires no Clerk account or login" to "No Clerk account or login required". (#9531) by @​eatmorespinach

• Fix an issue where sign-ups that used an enterprise SSO connection did not correctly forward redirect URLs. (#9449) by @​zourzouvillys

@​clerk/shared@​4.29.3

Patch Changes

• Update missing and invalid key error messages to recommend the Clerk CLI: npx clerk@latest init (non-interactive, no Clerk account required) to create an application, npx clerk@latest env pull to fetch the keys of an existing one, and npx clerk@latest deploy / npx clerk@latest env pull --instance prod for production. This covers both the errorThrower messages and the errors thrown by parsePublishableKey(key, { fatal: true }), which previously surfaced server-side as a bare Publishable key not valid. The Dashboard link is kept for manual key copying. (#9491) by @​djgould

@​clerk/shared@​4.29.2

Patch Changes

• Display a proper message when a password is rejected for matching one of the account's identifiers. Previously this error rendered as the incomplete sentence "Your password must contain ." on sign-up, reset password, and the user profile password form. The new message is available under the unstable__errors.form_password_matches_identifier localization key, and any password error the UI does not recognize now falls back to the message returned by the API instead of an empty sentence. (#9453) by @​dmoerner

Changelog

Sourced from @​clerk/shared's changelog.

4.30.1

Patch Changes

• Fix an issue where a verification that was still progressing normally could be cancelled and reported to the user as having timed out. (#9527) by @​zourzouvillys

4.30.0

Minor Changes

• Fixes an issue where OAuth account transfers that needed additional verification were returned to the beginning of sign-in. (#9497) by @​zourzouvillys

Patch Changes

• Keep Clerk's navigation inside the renderer. ClerkProvider now always supplies routerPush/routerReplace, so Clerk routes through your application's router when you provide one, and never navigates the window to an internal /CLERK-ROUTER/VIRTUAL/... path — which no custom protocol handler can serve, and which reloaded the renderer and dropped the user out of sign-in. (#9530) by @​jeremy-clerk

  Applications that worked around this by passing no-op router functions, or by filtering CLERK-ROUTER/VIRTUAL out themselves, can remove those workarounds.

• Polish the missing/invalid key error copy: drop the two-space indent before the npx clerk@latest init command (it rendered as a stray space in browser error overlays), start the follow-up sentence with the command name instead of "It" so the sentence stands on its own, and reword "Requires no Clerk account or login" to "No Clerk account or login required". (#9531) by @​eatmorespinach

• Fix an issue where sign-ups that used an enterprise SSO connection did not correctly forward redirect URLs. (#9449) by @​zourzouvillys

4.29.3

Patch Changes

• Update missing and invalid key error messages to recommend the Clerk CLI: npx clerk@latest init (non-interactive, no Clerk account required) to create an application, npx clerk@latest env pull to fetch the keys of an existing one, and npx clerk@latest deploy / npx clerk@latest env pull --instance prod for production. This covers both the errorThrower messages and the errors thrown by parsePublishableKey(key, { fatal: true }), which previously surfaced server-side as a bare Publishable key not valid. The Dashboard link is kept for manual key copying. (#9491) by @​djgould

4.29.2

Patch Changes

• Display a proper message when a password is rejected for matching one of the account's identifiers. Previously this error rendered as the incomplete sentence "Your password must contain ." on sign-up, reset password, and the user profile password form. The new message is available under the unstable__errors.form_password_matches_identifier localization key, and any password error the UI does not recognize now falls back to the message returned by the API instead of an empty sentence. (#9453) by @​dmoerner

Commits

• 2799f0d ci(repo): Version packages (#9538)
• dbaa95a fix(clerk-js,react,shared,ui): bound loading a verification, not running one ...
• 27dbf26 ci(repo): Version packages (#9521)
• 28b77ac fix(electron,shared,ui): keep Clerk navigation inside the Electron renderer (...
• 46bf7ce feat(shared): polish missing/invalid key error copy (#9531)
• e21ae9a docs(shared,ui): address the review comments from #9449 (#9522)
• 8bc1c9f fix(clerk-js,react,shared,ui): resume an OAuth transfer after a verification ...
• 17b865b fix(ui): populate enterprise SSO redirect urls when continuing a sign-up (#9449)
• 297c03d ci(repo): Version packages (#9514)
• ea8cb05 feat(shared): point missing and invalid key errors at the Clerk CLI (#9491)
• Additional commits viewable in compare view

[changeset-bot]

⚠️ No Changeset found

Latest commit: e815ae8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[dependabot]

Bumps @clerk/shared from 4.29.1 to 4.30.1.

Release notes

Sourced from @​clerk/shared's releases.

@​clerk/shared@​4.30.1

Patch Changes

• Fix an issue where a verification that was still progressing normally could be cancelled and reported to the user as having timed out. (#9527) by @​zourzouvillys

@​clerk/shared@​4.30.0

Minor Changes

• Fixes an issue where OAuth account transfers that needed additional verification were returned to the beginning of sign-in. (#9497) by @​zourzouvillys

Patch Changes

• Keep Clerk's navigation inside the renderer. ClerkProvider now always supplies routerPush/routerReplace, so Clerk routes through your application's router when you provide one, and never navigates the window to an internal /CLERK-ROUTER/VIRTUAL/... path — which no custom protocol handler can serve, and which reloaded the renderer and dropped the user out of sign-in. (#9530) by @​jeremy-clerk

  Applications that worked around this by passing no-op router functions, or by filtering CLERK-ROUTER/VIRTUAL out themselves, can remove those workarounds.

• Polish the missing/invalid key error copy: drop the two-space indent before the npx clerk@latest init command (it rendered as a stray space in browser error overlays), start the follow-up sentence with the command name instead of "It" so the sentence stands on its own, and reword "Requires no Clerk account or login" to "No Clerk account or login required". (#9531) by @​eatmorespinach

• Fix an issue where sign-ups that used an enterprise SSO connection did not correctly forward redirect URLs. (#9449) by @​zourzouvillys

@​clerk/shared@​4.29.3

Patch Changes

• Update missing and invalid key error messages to recommend the Clerk CLI: npx clerk@latest init (non-interactive, no Clerk account required) to create an application, npx clerk@latest env pull to fetch the keys of an existing one, and npx clerk@latest deploy / npx clerk@latest env pull --instance prod for production. This covers both the errorThrower messages and the errors thrown by parsePublishableKey(key, { fatal: true }), which previously surfaced server-side as a bare Publishable key not valid. The Dashboard link is kept for manual key copying. (#9491) by @​djgould

@​clerk/shared@​4.29.2

Patch Changes

• Display a proper message when a password is rejected for matching one of the account's identifiers. Previously this error rendered as the incomplete sentence "Your password must contain ." on sign-up, reset password, and the user profile password form. The new message is available under the unstable__errors.form_password_matches_identifier localization key, and any password error the UI does not recognize now falls back to the message returned by the API instead of an empty sentence. (#9453) by @​dmoerner

Changelog

Sourced from @​clerk/shared's changelog.

4.30.1

Patch Changes

• Fix an issue where a verification that was still progressing normally could be cancelled and reported to the user as having timed out. (#9527) by @​zourzouvillys

4.30.0

Minor Changes

• Fixes an issue where OAuth account transfers that needed additional verification were returned to the beginning of sign-in. (#9497) by @​zourzouvillys

Patch Changes

• Keep Clerk's navigation inside the renderer. ClerkProvider now always supplies routerPush/routerReplace, so Clerk routes through your application's router when you provide one, and never navigates the window to an internal /CLERK-ROUTER/VIRTUAL/... path — which no custom protocol handler can serve, and which reloaded the renderer and dropped the user out of sign-in. (#9530) by @​jeremy-clerk

  Applications that worked around this by passing no-op router functions, or by filtering CLERK-ROUTER/VIRTUAL out themselves, can remove those workarounds.

• Polish the missing/invalid key error copy: drop the two-space indent before the npx clerk@latest init command (it rendered as a stray space in browser error overlays), start the follow-up sentence with the command name instead of "It" so the sentence stands on its own, and reword "Requires no Clerk account or login" to "No Clerk account or login required". (#9531) by @​eatmorespinach

• Fix an issue where sign-ups that used an enterprise SSO connection did not correctly forward redirect URLs. (#9449) by @​zourzouvillys

4.29.3

Patch Changes

• Update missing and invalid key error messages to recommend the Clerk CLI: npx clerk@latest init (non-interactive, no Clerk account required) to create an application, npx clerk@latest env pull to fetch the keys of an existing one, and npx clerk@latest deploy / npx clerk@latest env pull --instance prod for production. This covers both the errorThrower messages and the errors thrown by parsePublishableKey(key, { fatal: true }), which previously surfaced server-side as a bare Publishable key not valid. The Dashboard link is kept for manual key copying. (#9491) by @​djgould

4.29.2

Patch Changes

• Display a proper message when a password is rejected for matching one of the account's identifiers. Previously this error rendered as the incomplete sentence "Your password must contain ." on sign-up, reset password, and the user profile password form. The new message is available under the unstable__errors.form_password_matches_identifier localization key, and any password error the UI does not recognize now falls back to the message returned by the API instead of an empty sentence. (#9453) by @​dmoerner

Commits

• 2799f0d ci(repo): Version packages (#9538)
• dbaa95a fix(clerk-js,react,shared,ui): bound loading a verification, not running one ...
• 27dbf26 ci(repo): Version packages (#9521)
• 28b77ac fix(electron,shared,ui): keep Clerk navigation inside the Electron renderer (...
• 46bf7ce feat(shared): polish missing/invalid key error copy (#9531)
• e21ae9a docs(shared,ui): address the review comments from #9449 (#9522)
• 8bc1c9f fix(clerk-js,react,shared,ui): resume an OAuth transfer after a verification ...
• 17b865b fix(ui): populate enterprise SSO redirect urls when continuing a sign-up (#9449)
• 297c03d ci(repo): Version packages (#9514)
• ea8cb05 feat(shared): point missing and invalid key errors at the Clerk CLI (#9491)
• Additional commits viewable in compare view

[changeset-bot]

⚠️ No Changeset found

Latest commit: e815ae8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR