Skip to content
Open
Changes from all commits
Commits
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 package.json
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,7 @@
"marked": "7.0.5",
"marked-react": "2.0.0",
"nanoid": "5.1.2",
"next": "14.2.35",
"next": "15.5.10",

Copilot AI Jan 28, 2026

Copy link

Choose a reason for hiding this comment

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

Next.js 15 officially recommends React 19, though it maintains backward compatibility with React 18. The current React version (18.3.1) may work, but you might encounter deprecation warnings or miss out on optimizations. Consider upgrading React and React DOM to version 19 alongside this Next.js upgrade for the best compatibility and to take advantage of React 19's features like the React Compiler and improved Server Components support. If staying on React 18, thoroughly test all interactive and server components.

Copilot uses AI. Check for mistakes.

Copilot AI Jan 28, 2026

Copy link

Choose a reason for hiding this comment

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

Verify that @sentry/nextjs version 9.4.0 is compatible with Next.js 15.5.10. Sentry has been releasing updates to support Next.js 15, and version 9.4.0 was released before Next.js 15.5.10. Check the Sentry changelog and consider updating to the latest @sentry/nextjs version to ensure full compatibility, particularly for instrumentation hooks, error tracking in Server Components, and the tunnelRoute configuration used in your next.config.mjs.

Copilot uses AI. Check for mistakes.

Copilot AI Jan 28, 2026

Copy link

Choose a reason for hiding this comment

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

This upgrade from Next.js 14.2.35 to 15.5.10 is a major version change that introduces breaking changes requiring code modifications throughout the codebase:

  1. params is now async: In Next.js 15, route segment params must be awaited. Currently, multiple pages access params synchronously (e.g., apps/shell/src/app/[locale]/layout.tsx:79, apps/shell/src/app/[locale]/governance/proposal/[id]/page.tsx:17-21, apps/shell/src/app/[locale]/staking/validator/[address]/page.tsx:18). These need to be updated to const { locale } = await params pattern.

  2. headers() returns a Promise: In Next.js 15, the headers() function returns a Promise and must be awaited. Currently used synchronously in multiple files (e.g., apps/shell/src/app/[locale]/layout.tsx:81, apps/shell/src/app/[locale]/page.tsx:18, apps/shell/src/app/[locale]/authz/page.tsx:17).

  3. Route handler params are async: API route handlers also need to await params (e.g., apps/shell/src/app/api/liquid-staking/unbondings/[address]/route.ts:23).

One file (apps/shell/src/app/[locale]/waitlist/page.tsx) already uses the correct async pattern, but all other pages need updates. These changes should be made before deploying this version to avoid runtime errors.

Suggested change
"next": "15.5.10",
"next": "14.2.35",

Copilot uses AI. Check for mistakes.
"next-intl": "3.26.5",

Copilot AI Jan 28, 2026

Copy link

Choose a reason for hiding this comment

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

The next-intl version (3.26.5) may not be fully compatible with Next.js 15.5.10. According to the next-intl documentation, Next.js 15 support was added in next-intl 3.16.0, but there have been ongoing compatibility updates. Consider updating next-intl to the latest version (3.x series) to ensure full compatibility with Next.js 15.5.10, as there may have been important fixes for Next.js 15 support since version 3.26.5 was released.

Copilot uses AI. Check for mistakes.
"posthog-js": "1.229.0",
"prettier-plugin-solidity": "2.2.1",
Expand Down
Loading