Uh oh!
There was an error while loading. Please reload this page.
Version Packages (alpha-v5) - #2366
Merged
Merged
Conversation
dimkl
approved these changes
Dec 14, 2023
dimkl
enabled auto-merge
December 14, 2023 23:53
dimkl
added this pull request to the merge queue
Dec 14, 2023
github-merge-queueBot
removed this pull request from the merge queue due to failed status checks
Dec 15, 2023
Uh oh!
There was an error while loading. Please reload this page.
This file contains hidden or 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
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
mainis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonmain.Releases
@clerk/backend@1.0.0-alpha-v5.9
Major Changes
@clerk/nextjs@5.0.0-alpha-v5.11
Major Changes
Drop support for NextJS v12: v12 was released on 26 Oct 2021. Support for security updates stopped on 21 Nov 2022. (#2347) by @nikosdouvlis
Drop support for NextJS <13.0.4: Various header-related bugs were introduced with the 12.1.0, 12.2.0, 13.0.1, 13.0.2, 13.0.3 NextJS releases which are now fixed since next@^13.0.4. We will be dropping support for these problematic versions in order to greatly reduce complexity in our codebase.
Drop support for NextJS < 14.0.3 because of the issues described here: Infinite redirect loop in NextJS development environment #1436.
Deprecate
authMiddlewarein favor ofclerkMiddleware. For more information, see https://clerk.com/docs/upgrade-guides/v5-introductionMove the server-side APIs from
@clerk/nextjsto the@clerk/nextjs/servermodule:WebhookEventType,WebhookEvent,verifyToken,redirectToSignIn,auth,buildClerkProps,clerkClient,currentUser,getAuth,redirectToSignUpandauthMiddleware. For more information, see https://clerk.com/docs/upgrade-guides/v5-introductionPatch Changes
e602d6c1f]:@clerk/fastify@1.0.0-alpha-v5.11
Patch Changes
e602d6c1f]:gatsby-plugin-clerk@5.0.0-alpha-v5.11
Patch Changes
e602d6c1f]:@clerk/remix@4.0.0-alpha-v5.11
Patch Changes
e602d6c1f]:@clerk/clerk-sdk-node@5.0.0-alpha-v5.9
Patch Changes
e602d6c1f]: