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 contains the following updates:
12.0.4
->12.0.7
12.0.4
->12.0.7
Release Notes
vercel/next.js
v12.0.7
Compare Source
Core Changes
Credits
Huge thanks to @timneutkens for helping!
v12.0.6
Compare Source
Core Changes
v12.0.5
Compare Source
This upgrade is completely backward-compatible and recommended for all users on versions below 12.0.5. A backport of the patch to Next.js 11 is available as 11.1.3.
When a URL is provided to
next-server
that cannot be parsed, anunhandledPromiseRejection
could occur. On Node.js versions <v15.0.0
this isn't a fatal issue as only a warning is shown. However, in Node.js versions >v15.0.0
, this causes the server process to exit, which can result in unexpected server crashes.How to Upgrade
npm install next@latest --save
Impact
v11.1.0
and belowv12.0.5
v15.0.0
being usednext start
or a custom serverWe recommend everyone to upgrade regardless of whether you can reproduce the issue or not.
How to Assess Impact
If you are running Node.js >
v15.0.0
with Next.js, you can filter any server error logs forERR_INVALID_URL
.What is Being Done
As Next.js has grown in popularity and usage by enterprises, it has received the attention of security researchers and auditors. We are thankful to GitHub user
hopeless-programmer-online
for their investigation and discovery of the original bug.We've landed a patch that ensures this is handled properly so the
unhandledPromiseRejection
issue no longer occurs.Regression tests for this attack were added to the security integration test suite
[email protected]
. We are actively monitoring this mailbox.Core Changes
console.*
calls.: #31449next lint
withouteslint-config-next
installed: #29823.json
static method: #31483Google-PageRenderer
bot: #31521Document
components an error: #31505renderToWebStream
: #31553no-html-link-for-pages
from warning for static files: #31495next/link
: #30606pages/_document
: #31946Documentation Changes
Suspense
import: #31897React
import: #31900next export
documentation.: #31465sharp
memory usage on default Linux setup: #31919Example Changes
with-sentry
example: #30401Misc Changes
Credits
Huge thanks to @mzaien, @losfair, @ykzts, @leerob, @timneutkens, @stefanprobst, @javivelasco, @sokra, @goncy, @knezevicdev, @Kikobeats, @huozhi, @shuding, @styfle, @yang-feng-yfeng, @kdy1, @xuchaobei, @elkevinwolf, @padmaia, @kyliau, @devknoll, @fabienheureux, @hanneslund, @nilskaspersson, @Andarist, @mathcrln, @ijjk, @dferber90, @molebox, @FranciscoMoretti, @benschwarz, @wendellhu95, @gazdagergo, @imabp, @ljosberinn, @samuliasmala, @lfades, @ka2jun8, @monsonjeremy, @pqt, @vvo, @leoortizz, @michel-kraemer, @thibautsabot, @MaedahBatool, @lobsterkatie, @ntkoopman, @delbaoliveira, @iicdii, @j-mendez, @chentsulin, @ericmatthys, @lennym, @balogunkeji, and @wnr for helping!
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by WhiteSource Renovate. View repository job log here.