Conversation
|
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9603d2a7d1
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "version": "14.0.4", | ||
| "resolved": "https://registry.npmjs.org/next/-/next-14.0.4.tgz", | ||
| "integrity": "sha512-qbwypnM7327SadwFtxXnQdGiKpkuhaRLE2uq62/nRul9cj9KhQ5LhHmlziTNqUidZotw/Q1I9OjirBROdUJNgA==", | ||
| "deprecated": "This version has a security vulnerability. Please upgrade to a patched version. See https://nextjs.org/blog/security-update-2025-12-11 for more details.", |
There was a problem hiding this comment.
Upgrade Next.js to a patched release
This change pins next to 14.0.4, and the lockfile itself marks that exact version as deprecated due to a known security vulnerability. Because the Node.js Next.js weblog image installs from this lockfile, CI and local test runs will continue using a known-vulnerable framework version until it is bumped. Please move to a patched Next.js release and regenerate the lockfile so the test image no longer ships vulnerable dependencies.
Useful? React with 👍 / 👎.
BridgeAR
left a comment
There was a problem hiding this comment.
LGTM since this is indeed an update from 13.5.4 due to the package-lock.json update
Motivation
Upgrade to nextjs 14.0.4 for support for manual signal handler setup, see #6814
Changes
Workflow
🚀 Once your PR is reviewed and the CI green, you can merge it!
🛟 #apm-shared-testing 🛟
Reviewer checklist
tests/ormanifests/is modified ? I have the approval from R&P teambuild-XXX-imagelabel is present