Uh oh!
There was an error while loading. Please reload this page.
chore: lock nextjs to 13.2.0 (#5301 - #5301
Merged
ovflowd merged 1 commit intoApr 19, 2023
Merged
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
ovflowd
commented
Apr 19, 2023
MemberAuthor
I will fast-merge this as soon as deployment ends, as this is critical for speeding up our Vercel deployments. cc @nodejs/website |
ovflowd added a commit
that referenced
this pull request
May 3, 2023
chore: next lock to versin 13.2.0
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
1 participant
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 locks Next.js to 13.2.0 as any version higher than 13.2.0 introduces an issue with Vercel Deployments not being able to use Cache.
This seems to be a https://github.com/shuding/nextra bug and it is reported here: shuding/nextra#1564