Update dependency next to v15.2.3 [SECURITY]#40
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
bbdab52 to
cddae99
Compare
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 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.
This PR contains the following updates:
15.1.7->15.2.3GitHub Vulnerability Alerts
CVE-2025-29927
Impact
It is possible to bypass authorization checks within a Next.js application, if the authorization check occurs in middleware.
Patches
15.2.314.2.2513.5.912.3.5Note: Next.js deployments hosted on Vercel are automatically protected against this vulnerability.
Workaround
If patching to a safe version is infeasible, it is recommend that you prevent external user requests which contain the
x-middleware-subrequestheader from reaching your Next.js application.Credits
Release Notes
vercel/next.js (next)
v15.2.3Compare Source
v15.2.2Compare Source
Core Changes
d55cc79b-20250228to443b7ff2-20250303: #76804443b7ff2-20250303toe03ac20f-20250305: #76842__next_app__module loading functions: #74566e03ac20f-20250305to029e8bd6-20250306: #76870xbutton present: #76898Example Changes
Misc Changes
redirectin client components: #76332labeler.json: #76828SyntaxContextfor__turbopack_esm__: #73544next.browserinstead ofwebdriverin pages/ client-navigation: #76867swc_coretov16.4.0: #76596v1.0.0-alpha.64: #76856__dirname: #76902Credits
Huge thanks to @pranathip, @gaojude, @ijjk, @eps1lon, @Nayeem-XTREME, @leerob, @styfle, @samcx, @sokra, @huozhi, @raunofreiberg, @mischnic, @lubieowoce, @unstubbable, @ztanner, @kdy1, @timneutkens, @wbinnssmith, @bgw, and @oscr for helping!
v15.2.1Compare Source
Core Changes
sourcePackagereferences: #76550revalidateproperty from incremental cachectxforFETCHkind: #76500cache-controlheader and prerender manifest: #762075.8.2: #76709generateStaticParams: #7671322e39ea7-20250225tod55cc79b-20250228: #76680Example Changes
paramscode blocks: #76705Misc Changes
swc_coretov16.0.0: #76414parallel-routes-revalidationtest: #76600octokit.rest.issues.addLabelscall: #76601devIndicatorsand note on deprecated options: #76611htmlLimitedBotsoption: #76616test-turbopack-integrationnot having any shards : #76355describeVariantshelper: #76631toDisplayRedbox(): replace all occurrences of testDir: #76618Credits
Huge thanks to @acdlite, @bgw, @ijjk, @molebox, @kdy1, @timneutkens, @devjiwonchoi, @mischnic, @unstubbable, @eps1lon, @huozhi, @philipithomas, @delbaoliveira, @samcx, @wbinnssmith, @sokra, @gnoff, @leerob, @ztanner, @raunofreiberg, @lubieowoce, and @LihaoWang for helping!
v15.2.0Compare Source
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - 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 this update again.
This PR was generated by Mend Renovate. View the repository job log.