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 #4968

Merged
merged 1 commit into from
Jan 23, 2025
Merged

ci(repo): Version packages #4968

merged 1 commit into from
Jan 23, 2025

Conversation

clerk-cookie
Copy link
Collaborator

@clerk-cookie clerk-cookie commented Jan 22, 2025

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]

Major Changes

  • No changes have been made to the SDK in this update. There are no breaking changes. (#4966) by @LekoArts

    This merely bumps the version to a non-zero range and moves the SDK out of beta to a stable release.

Patch Changes

@clerk/[email protected]

Minor Changes

  • Add experimental support for listening to cookie changes on a synced host via the __experimental_syncHostListener (#4962) by @tmilewski

Patch Changes

@clerk/[email protected]

Minor Changes

    • Introduced an upsert method to the SignUp resource, which reuses the existing sign-up attempt ID if it exists. (#4720) by @kostaspt

    • Fix a ticket flow issue on <SignUp /> component, where in some rare cases the initial ticket/context is lost, because of creating a new sign-up attempt ID.

  • Expand Keyless popover when a user signs-in. (#4969) by @kaftarmery

Patch Changes

@clerk/[email protected]

Minor Changes

    • Introduced an upsert method to the SignUp resource, which reuses the existing sign-up attempt ID if it exists. (#4720) by @kostaspt

    • Fix a ticket flow issue on <SignUp /> component, where in some rare cases the initial ticket/context is lost, because of creating a new sign-up attempt ID.

@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

Copy link

vercel bot commented Jan 22, 2025

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 Jan 23, 2025 0:26am

@github-actions github-actions bot force-pushed the changeset-release/main branch from 0942371 to 410ae6c Compare January 22, 2025 14:36
@github-actions github-actions bot force-pushed the changeset-release/main branch from 410ae6c to dfc5d3f Compare January 22, 2025 14:57
@github-actions github-actions bot force-pushed the changeset-release/main branch from dfc5d3f to 9696cf4 Compare January 22, 2025 15:17
@github-actions github-actions bot force-pushed the changeset-release/main branch from 9696cf4 to d8740ec Compare January 22, 2025 16:05
@github-actions github-actions bot force-pushed the changeset-release/main branch from d8740ec to e5399b7 Compare January 22, 2025 17:08
@github-actions github-actions bot force-pushed the changeset-release/main branch from e5399b7 to fcbd699 Compare January 22, 2025 17:24
@github-actions github-actions bot force-pushed the changeset-release/main branch from fcbd699 to 8506ecd Compare January 22, 2025 18:41
@github-actions github-actions bot force-pushed the changeset-release/main branch from 8506ecd to aa96e7e Compare January 22, 2025 19:59
@github-actions github-actions bot force-pushed the changeset-release/main branch from aa96e7e to 929754b Compare January 22, 2025 22:20
@github-actions github-actions bot force-pushed the changeset-release/main branch from 929754b to 5a55073 Compare January 23, 2025 08:55
@nikosdouvlis nikosdouvlis reopened this Jan 23, 2025
@nikosdouvlis nikosdouvlis merged commit 5b4c220 into main Jan 23, 2025
29 checks passed
@nikosdouvlis nikosdouvlis deleted the changeset-release/main branch January 23, 2025 12:36
wobsoriano pushed a commit that referenced this pull request Feb 8, 2025
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
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.

None yet

2 participants