Skip to content

chore(deps): bump next from 16.2.6 to 16.2.7 #44

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.

Sign up for GitHub

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

Open
dependabot wants to merge 1 commit into
base: main
Choose a base branch
from
+47 −47
Open

chore(deps): bump next from 16.2.6 to 16.2.7 #44

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion apps/web/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@
"js-yaml": "^4.1.0",
"jszip": "^3.10.1",
"katex": "^0.17.0",
"next": "16.2.6",
"next": "16.2.7",
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot Jun 4, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🌐 Web query:

Is Next.js version 16.2.7 a valid release and what are its requirements for React compatibility?

💡 Result:

Yes. Next.js v16.2.7 is a real, published release. 1) Is 16.2.7 a valid release? Next.js v16.2.7 exists as an official GitHub release tag in the vercel/next.js repository [1] and is also available on npm as version 16.2.7 [2]. The GitHub release notes label it as a “backporting bug fixes” patch release [1]. 2) React compatibility requirements for Next.js 16.2.7 - Next.js 16’s App Router uses the React canary channel internally; the Next.js v16 upgrade documentation states that the App Router in Next.js 16 uses the “latest React Canary release” [3]. - Next.js expects the installed react and react-dom packages to match exactly (version strings must be the exact same). The Next.js repo contains logic that throws an “Incompatible React versions” error when the react and react-dom versions differ [4]. Practical requirement for React versions: - Install react and react-dom at the exact same version (and align with the React canary expectations described for Next.js 16’s App Router) [3][4]. Notes: - This does not mean you must use React stable; it indicates Next.js 16’s App Router targets the canary stream and Next.js will error on mismatched react vs react-dom versions [3][4].

Citations:

🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Show package.json dependency versions around the Next.js entry
sed -n '1,120p' apps/web/package.json | nl -ba | sed -n '1,120p'

# Extract specific dependency lines for clarity
rg -n '"next"|eslint-config-next|react-dom|react' apps/web/package.json || true

# Check pnpm-lock.yaml for next@16.2.7 and eslint-config-next entries
if [ -f apps/web/pnpm-lock.yaml ]; then
  rg -n 'next@16\.2\.7|next@16\.2\.6|eslint-config-next' apps/web/pnpm-lock.yaml | head -n 80
else
  echo "Missing apps/web/pnpm-lock.yaml"
fi

Repository: OpenDevFlow/md-latex

Length of output: 107

🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Confirm files exist
ls -la apps/web/package.json apps/web/pnpm-lock.yaml >/dev/null 2>&1 || {
  echo "Missing apps/web/package.json and/or apps/web/pnpm-lock.yaml"
  ls -la apps/web || true
  exit 1
}

echo "=== apps/web/package.json (first 120 lines) ==="
sed -n '1,120p' apps/web/package.json

echo
echo "=== Version lines for next/react/eslint-config-next ==="
rg -n '"(next|react-dom|react|eslint-config-next)"\s*:' apps/web/package.json || true

echo
echo "=== pnpm-lock.yaml entries for next@16.2.6/16.2.7 and eslint-config-next ==="
rg -n 'next@16\.2\.(6|7)\b|eslint-config-next@16\.2\.6\b' apps/web/pnpm-lock.yaml | head -n 200 || true

echo
echo "=== pnpm-lock.yaml peer dependency hints (search nearby for eslint-config-next) ==="
rg -n 'eslint-config-next@16\.2\.6' apps/web/pnpm-lock.yaml | head -n 20 || true

Repository: OpenDevFlow/md-latex

Length of output: 2395

🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Print the eslint-config-next@16.2.6 block from pnpm-lock.yaml (peer deps section)
# Use sed to keep output bounded.
echo "=== pnpm-lock.yaml: eslint-config-next@16.2.6 block (around line 1151) ==="
sed -n '1120,1205p' apps/web/pnpm-lock.yaml

echo
echo "=== pnpm-lock.yaml: eslint-config-next@16.2.6(<peer deps>) block (around line 3422) ==="
sed -n '3390,3485p' apps/web/pnpm-lock.yaml

echo
echo "=== pnpm-lock.yaml: next@16.2.6 block (around line 1795) ==="
sed -n '1765,1845p' apps/web/pnpm-lock.yaml

echo
echo "=== pnpm-lock.yaml: next@16.2.6 react peer resolution (around line 4166) ==="
sed -n '4130,4195p' apps/web/pnpm-lock.yaml

# Also locate next@16.2.7 and print its block
echo
echo "=== pnpm-lock.yaml: locating next@16.2.7 ==="
rg -n 'next@16\.2\.7\b' apps/web/pnpm-lock.yaml || true

Repository: OpenDevFlow/md-latex

Length of output: 12432

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "=== next@16.2.7 occurrences in pnpm-lock.yaml ==="
rg -n 'next@16\.2\.7\b' apps/web/pnpm-lock.yaml || true

echo
echo "=== next@16.2.7 block context (if present) ==="
line="$(rg -n 'next@16\.2\.7\b' apps/web/pnpm-lock.yaml | head -n 1 | cut -d: -f1 || true)"
if [ -n "${line:-}" ]; then
  start=$((line-40))
  end=$((line+80))
  sed -n "${start},${end}p" apps/web/pnpm-lock.yaml
else
  echo "No next@16.2.7 entry found in pnpm-lock.yaml."
fi

Repository: OpenDevFlow/md-latex

Length of output: 208

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "=== occurrences of 16.2.7 in pnpm-lock.yaml ==="
rg -n '\b16\.2\.7\b' apps/web/pnpm-lock.yaml | head -n 50 || true

echo
echo "=== occurrences of next@16.*.7 in pnpm-lock.yaml ==="
rg -n 'next@16\.[0-9]+\.[0-9]+(\(|:)' apps/web/pnpm-lock.yaml | head -n 50 || true

echo
echo "=== occurrences of next@16.2.7 with peer-suffix patterns (extra search) ==="
rg -n 'next@16\.2\.7\(' apps/web/pnpm-lock.yaml || true

echo
echo "=== package.json declared next version ==="
rg -n '"next"\s*:' apps/web/package.json

Repository: OpenDevFlow/md-latex

Length of output: 610

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "=== occurrences of react@19.2.6 and react-dom@19.2.6 in pnpm-lock.yaml ==="
rg -n '\breact@19\.2\.6\b|\breact-dom@19\.2\.6\b' apps/web/pnpm-lock.yaml | head -n 50 || true

echo
echo "=== occurrences of react@19.2.4 and react-dom@19.2.4 in pnpm-lock.yaml ==="
rg -n '\breact@19\.2\.4\b|\breact-dom@19\.2\.4\b' apps/web/pnpm-lock.yaml | head -n 50 || true

Repository: OpenDevFlow/md-latex

Length of output: 831

Fix pnpm-lock mismatch for Next.js 16.2.7

  • next@16.2.7 is a real release and its React peer range includes React 19.x (so react@19.2.6 is acceptable).
  • apps/web/pnpm-lock.yaml does not include next@16.2.7 (it only has next@16.2.6), and it does not include react@19.2.6 (it only has react@19.2.4), so installs will likely resolve older versions than apps/web/package.json declares (see apps/web/package.json:27 vs apps/web/pnpm-lock.yaml).
  • eslint-config-next@16.2.6 only peers eslint/typescript (no React compatibility constraint), but aligning it with next@16.2.7 is still preferable.
🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@apps/web/package.json` at line 27, package.json declares "next": "16.2.7"
(and React 19.x compatibility) but apps/web/pnpm-lock.yaml still pins
next@16.2.6 and react@19.2.4; regenerate the lockfile so installs match
package.json: update the dependency entries to next@16.2.7 and react@19.2.6 and
align eslint-config-next to 16.2.7, then run pnpm install (or pnpm install
--lockfile-only) in apps/web to update apps/web/pnpm-lock.yaml so it contains
the new resolved versions.

"react": "19.2.6",
"react-dom": "19.2.6",
"rehype-katex": "^7.0.1",
Expand Down
92 changes: 46 additions & 46 deletions pnpm-lock.yaml
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading