-
Notifications
You must be signed in to change notification settings - Fork 48
fix(deps): update dependency next to v14.2.25 [security] #1933
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
base: dev
Are you sure you want to change the base?
Conversation
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
✅ Deploy Preview for kleros-v2-testnet canceled.
|
✅ Deploy Preview for kleros-v2-testnet-devtools canceled.
|
✅ Deploy Preview for kleros-v2-university canceled.
|
✅ Deploy Preview for kleros-v2-neo canceled.
|
9e43280
to
985d0ee
Compare
659b719
to
077e0b8
Compare
a78d534
to
1e84bb3
Compare
1e84bb3
to
d7b20ce
Compare
Code Climate has analyzed commit d7b20ce and detected 0 issues on this pull request. View more on Code Climate. |
|
This PR contains the following updates:
14.2.21
->14.2.25
GitHub 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.3
14.2.25
13.5.9
12.3.5
Note: 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-subrequest
header from reaching your Next.js application.Credits
Release Notes
vercel/next.js (next)
v14.2.25
Compare Source
v14.2.24
Compare Source
Core Changes
Credits
Huge thanks to @ztanner for helping!
v14.2.23
Compare Source
Core Changes
Credits
Huge thanks to @styfle, @ijjk and @lubieowoce for helping!
v14.2.22
Compare Source
Core Changes
Credits
Huge thanks to @unstubbable, @ijjk, and @ztanner for helping!
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 is behind base branch, 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.
PR-Codex overview
This PR focuses on updating the
next
package and its associated dependencies to version14.2.25
in thepackage.json
andyarn.lock
files. This ensures compatibility with the latest features and fixes.Detailed summary
next
from14.2.21
to14.2.25
inpackage.json
andyarn.lock
.@next/*
dependencies to version14.2.25
inyarn.lock
.next
version inyarn.lock
.