ci(repo): Version packages #5419
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
335aca6 to
9b8e7ec
Compare
nikosdouvlis
approved these changes
Mar 22, 2025
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
9b8e7ec to
c97b2c2
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
c97b2c2 to
74648a9
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
74648a9 to
ff5b010
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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/chrome-extension@2.2.20
Patch Changes
5601767]:@clerk/clerk-js@5.57.3
Patch Changes
@clerk/clerk-expo@2.9.3
Patch Changes
5601767]:@clerk/nextjs@6.12.9
Patch Changes
The majority of Clerk applications are not impacted by the NextJS vulnerability disclosed on 22 MAR 2025. Your application might be impacted if you're not using the latest NextJS release and you do not call auth() in your routes or pages. We still recommend upgrading to the latest NextJS version as soon as possible. (#5426) by @nikosdouvlis
For more details, please see https://clerk.com/blog/cve-2025-29927