chore(deps): bump the npm_and_yarn group across 3 directories with 1 update#13
chore(deps): bump the npm_and_yarn group across 3 directories with 1 update#13dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
…update Bumps the npm_and_yarn group with 1 update in the / directory: [next](https://github.com/vercel/next.js). Bumps the npm_and_yarn group with 1 update in the /apps/web directory: [next](https://github.com/vercel/next.js). Bumps the npm_and_yarn group with 1 update in the /packages/eslint-config directory: [next](https://github.com/vercel/next.js). Updates `next` from 14.2.35 to 16.1.5 - [Release notes](https://github.com/vercel/next.js/releases) - [Changelog](https://github.com/vercel/next.js/blob/canary/release.js) - [Commits](vercel/next.js@v14.2.35...v16.1.5) Updates `next` from 14.2.35 to 16.1.6 - [Release notes](https://github.com/vercel/next.js/releases) - [Changelog](https://github.com/vercel/next.js/blob/canary/release.js) - [Commits](vercel/next.js@v14.2.35...v16.1.5) Updates `next` from 14.2.35 to 16.1.5 - [Release notes](https://github.com/vercel/next.js/releases) - [Changelog](https://github.com/vercel/next.js/blob/canary/release.js) - [Commits](vercel/next.js@v14.2.35...v16.1.5) --- updated-dependencies: - dependency-name: next dependency-version: 16.1.5 dependency-type: direct:production dependency-group: npm_and_yarn - dependency-name: next dependency-version: 16.1.6 dependency-type: direct:production dependency-group: npm_and_yarn - dependency-name: next dependency-version: 16.1.5 dependency-type: direct:production dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
dependabot
bot
added
dependencies
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
| "devOptional": true, | ||
| "license": "Apache-2.0" | ||
| }, | ||
| "node_modules/@prisma/engines": { | ||
| "version": "5.22.0", | ||
| "resolved": "https://registry.npmjs.org/@prisma/engines/-/engines-5.22.0.tgz", | ||
| "integrity": "sha512-UNjfslWhAt06kVL3CjkuYpHAWSO6L4kDCVPegV6itt7nD1kSJavd3vhgAEhjglLJJKEdJ7oIqDJ+yHk6qO8gPA==", | ||
| "dev": true, | ||
| "devOptional": true, | ||
| "hasInstallScript": true, | ||
| "license": "Apache-2.0", | ||
| "dependencies": { |
There was a problem hiding this comment.
Bug: The Vercel deployment workflow uses Node.js 18, which is incompatible with the newly required Node.js version (>=20.9.0) for the upgraded Next.js dependency, causing deployment failures.
Severity: HIGH
Suggested Fix
Update the project's root package.json to enforce the new requirement by setting "engines": { "node": ">=20.9.0" }. Additionally, modify the Vercel deployment workflow at apps/web/.github/workflows/deploy.yml to use node-version: '20' instead of '18' to align the deployment environment with the dependency requirements.
Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.
Location: package-lock.json#L4607-L4620
Potential issue: The project's `package.json` specifies a minimum Node.js version of
`>=18.0.0`. However, this pull request upgrades Next.js to version 16.1.5, which
requires Node.js version `>=20.9.0`. A critical deployment workflow,
`apps/web/.github/workflows/deploy.yml`, is configured to use Node.js version 18. This
mismatch will cause the Vercel deployment to fail during the build step, as it will
attempt to run the new Next.js version on an unsupported Node.js runtime. While the main
CI pipeline uses Node.js 20 and will pass, the production deployment will be blocked.
Did we get this right? 👍 / 👎 to inform future reviews.
There was a problem hiding this comment.
Pull request overview
This PR updates Next.js from version 14.2.35 to 16.1.5/16.1.6 across multiple directories in the monorepo as part of a security update addressing CVE-2025-59471, CVE-2025-59472, and CVE-2026-23864. This is a major version upgrade that includes significant changes to Next.js's runtime requirements and dependencies.
Changes:
- Upgrades Next.js from 14.2.35 to 16.1.5 (in package-lock.json and packages/eslint-config) and 16.1.6 (in apps/web)
- Updates Next.js-related dependencies including SWC helpers, styled-jsx, and platform-specific binaries
- Changes minimum Node.js requirement from >=18.17.0 to >=20.9.0
Reviewed changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| apps/web/package.json | Updates Next.js to version 16.1.6 |
| packages/eslint-config/package.json | Updates Next.js to version 16.1.5 |
| package-lock.json | Updates lockfile with Next.js 16.1.5 and all related dependencies, removes deprecated packages (busboy, graceful-fs, win32-ia32-msvc), downgrades OpenTelemetry API to 1.7.0 at root level |
| "clsx": "^2.1.0", | ||
| "lucide-react": "^0.300.0", | ||
| "next": "^14.2.33", | ||
| "next": "^16.1.6", |
There was a problem hiding this comment.
Version inconsistency detected: This package specifies Next.js 16.1.6, but the package-lock.json and packages/eslint-config/package.json both use 16.1.5. All Next.js versions across the monorepo should be consistent to avoid potential dependency resolution issues and runtime inconsistencies. The PR description mentions updating to 16.1.5 and 16.1.6, but it's unclear why different versions are needed. Recommend aligning all packages to use the same version (preferably 16.1.6 if it contains additional security fixes).
| "next": "^16.1.6", | |
| "next": "^16.1.5", |
| "@ai-sdk/openai": "2.0.76", | ||
| "ai": "6.0.5", | ||
| "next": "14.2.35" | ||
| "next": "16.1.5" |
There was a problem hiding this comment.
Version inconsistency detected: This package specifies Next.js 16.1.5, while apps/web/package.json uses 16.1.6. All Next.js versions across the monorepo should be consistent to avoid potential dependency resolution issues. Recommend aligning all packages to use the same version (preferably 16.1.6 if it contains additional security fixes).
| "next": "16.1.5" | |
| "next": "16.1.6" |
1 participant
Bumps the npm_and_yarn group with 1 update in the / directory: next.
Bumps the npm_and_yarn group with 1 update in the /apps/web directory: next.
Bumps the npm_and_yarn group with 1 update in the /packages/eslint-config directory: next.
Updates
nextfrom 14.2.35 to 16.1.5Release notes
Sourced from next's releases.
... (truncated)
Commits
acba4a6v16.1.5e1d1fc6Add maximum size limit for postponed body parsing (#88175)500ec83fetch(next/image): reduce maximumResponseBody from 300MB to 50MB (#88588)1caaca3feat(next/image)!: addimages.maximumResponseBodyconfig (#88183)522ed84Sync DoS mitigations for React Flight8cad197[backport][cna] Ensure created app is not considered the workspace root in pn...2718661Backport/docs fixes (#89031)5333625Backport/docs fixes 16.1.5 (#88916)60de6c2v16.1.45f75d22backport: Only filter next config if experimental flag is enabled (#88733) (#...Updates
nextfrom 14.2.35 to 16.1.6Release notes
Sourced from next's releases.
... (truncated)
Commits
acba4a6v16.1.5e1d1fc6Add maximum size limit for postponed body parsing (#88175)500ec83fetch(next/image): reduce maximumResponseBody from 300MB to 50MB (#88588)1caaca3feat(next/image)!: addimages.maximumResponseBodyconfig (#88183)522ed84Sync DoS mitigations for React Flight8cad197[backport][cna] Ensure created app is not considered the workspace root in pn...2718661Backport/docs fixes (#89031)5333625Backport/docs fixes 16.1.5 (#88916)60de6c2v16.1.45f75d22backport: Only filter next config if experimental flag is enabled (#88733) (#...Updates
nextfrom 14.2.35 to 16.1.5Release notes
Sourced from next's releases.
... (truncated)
Commits
acba4a6v16.1.5e1d1fc6Add maximum size limit for postponed body parsing (#88175)500ec83fetch(next/image): reduce maximumResponseBody from 300MB to 50MB (#88588)1caaca3feat(next/image)!: addimages.maximumResponseBodyconfig (#88183)522ed84Sync DoS mitigations for React Flight8cad197[backport][cna] Ensure created app is not considered the workspace root in pn...2718661Backport/docs fixes (#89031)5333625Backport/docs fixes 16.1.5 (#88916)60de6c2v16.1.45f75d22backport: Only filter next config if experimental flag is enabled (#88733) (#...Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditionsYou can disable automated security fix PRs for this repo from the Security Alerts page.