Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci(repo): Version packages #4663

Merged
merged 1 commit into from
Dec 2, 2024
Merged

ci(repo): Version packages #4663

merged 1 commit into from
Dec 2, 2024

Conversation

clerk-cookie
Copy link
Collaborator

@clerk-cookie clerk-cookie commented Nov 27, 2024

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@clerk/[email protected]

Minor Changes

    • Update the supported API version to 2024-10-01 that includes the following changes (#4596) by @Nikpolik

      • Notification for new sign ins to users' accounts feature becomes available.
      • The response for Sign Ins with an email address that matches a SAML connection is updated. Instead of responding with a status of needs_identifier the API will now return a status of needs_first_factor and the email address that matched will be returned in the identifier field. the only strategy that will be included in supported first factors is enterprise_sso

      Read more in the API Version docs

    • Update components to use the new enterprise_sso strategy for sign ins / sign ups that match an enterprise connection and handle the new API response.

      This strategy supersedes SAML to provide a single strategy as the entry point for Enterprise SSO regardless of the underlying protocol used to authenticate the user.

      For now there are two new types of connections that are supported in addition to SAML, Custom OAuth and EASIE (multi-tenant OAuth).

Patch Changes

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

  • Add support for the new enterprise_sso strategy. (#4596) by @Nikpolik

    This strategy supersedes SAML to provide a single strategy as the entry point for Enterprise Single Sign On regardless of the underlying protocol used to authenticate the user.
    For now there are two new types of connections that are supported in addition to SAML, Custom OAuth and EASIE (multi-tenant OAuth).

    • Add a new user setting enterpriseSSO, this gets enabled when there is an active enterprise connection for an instance.
    • Add support for signing in / signing up with the new enterprise_sso strategy.
    • Deprecated userSettings.saml in favor of enterprise_sso.
    • Deprecated saml sign in strategy in favor of enterprise_sso.

@clerk/[email protected]

Patch Changes

@clerk/[email protected]

Patch Changes

Copy link

vercel bot commented Nov 27, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
clerk-js-sandbox ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 2, 2024 10:09am

@nikosdouvlis nikosdouvlis merged commit 237be1b into main Dec 2, 2024
29 checks passed
@nikosdouvlis nikosdouvlis deleted the changeset-release/main branch December 2, 2024 13:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants