-
-
Notifications
You must be signed in to change notification settings - Fork 112
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
[FEATURE] Update the packages in the repository #333
Comments
/help |
Hello, @ashmit-coder! 👋🏼 I'm 🧞🧞🧞 Genie 🧞🧞🧞 from the magic lamp. Looks like somebody needs a hand! At the moment the following comments are supported in issues:
|
Hello admin |
Am sorry but @jerensi is already working on it |
@ALIPHATICHYD, @jerensl has decided to step down, are you still interested in giving it a try? |
Yeah sure I can check it out |
@AceTheCreator can I work on this issue |
Yes go ahead @techmannih |
@ashmit-coder sure, Thank you! |
@techmannih please do work on one issue at a time. Atleast get one of the pr's through and then work on the other. So that others can work on it. |
@ashmit-coder Yeah got it |
Closing this issue, as it has been resolved |
Why do we need this improvement?
This should help us get rid of the security vulnarablities of the current
Next.js 12
and upgrade it toNext 14
How will this change help?
It will remove the version incomaptablities that may arise in the future.
Screenshots
How could it be implemented/designed?
Resource:- https://nvd.nist.gov/vuln/detail/CVE-2023-46298
🚧 Breaking changes
Yes
👀 Have you checked for similar open issues?
🏢 Have you read the Contributing Guidelines?
Are you willing to work on this issue?
No, someone else can work on it.
The text was updated successfully, but these errors were encountered: