Skip to content

chore(deps): bump next from 14.2.33 to 16.1.5 #133

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

Closed
dependabot wants to merge 1 commit into from
Closed

chore(deps): bump next from 14.2.33 to 16.1.5 #133

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/portal/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@
"moment": "^2.30.1",
"mux-embed": "^4.12.0",
"nanoid": "^5.0.7",
"next": "^14.2.32",
"next": "^16.1.5",
Copy link
Copy Markdown

@augmentcode augmentcode Bot Jan 31, 2026

Choose a reason for hiding this comment

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

This is a major Next.js upgrade (14 → 16); it’s worth verifying that the app’s react/react-dom and Node versions satisfy Next 16’s peer/runtime requirements. Also double-check any next.config.* options and middleware/app-router behavior the portal relies on still behave the same after the bump.

Fix This in Augment

🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.

Copy link
Copy Markdown

@augmentcode augmentcode Bot Jan 31, 2026

Choose a reason for hiding this comment

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

Minor metadata mismatch: the PR title says this bumps Next from 14.2.33, but this package.json entry was 14.2.32. If intentional that’s fine, but it can make auditing/version tracking confusing.

Fix This in Augment

🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.

Copy link
Copy Markdown
Contributor

@greptile-apps greptile-apps Bot Jan 31, 2026

Choose a reason for hiding this comment

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

Verify compatibility of next 16.1.5 with React 18.3.1. Next.js 16 introduced changes to React compatibility and may require testing all interactive features.

Prompt To Fix With AI 
This is a comment left during a code review.
Path: apps/portal/package.json
Line: 43:43

Comment:
Verify compatibility of `next` 16.1.5 with React 18.3.1. Next.js 16 introduced changes to React compatibility and may require testing all interactive features.

How can I resolve this? If you propose a fix, please make it concise.

"plyr": "^3.7.8",
"plyr-react": "^5.3.0",
"public-ip": "^4.0.4",
Expand Down
Loading