fix/downgrade next #2221
Merged
fix/downgrade next #2221
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
BCerki
approved these changes
Sep 18, 2024
marcellmueller
force-pushed
the
fix/downgrade-next
branch
from
13215f9
to
7f0302c
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.
Dependabot opened this minor version change. I pulled it, tested reg1 and bciers and it was working. Though once it merged I tried it again and was having some issues.
vercel/next.js#65412
Looks like it will be fixed soon, downgrading to the v14.2.10 from Brianna's earlier PR for now thanks!