Update Next.js version #8545
Update Next.js version #8545
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
WalkthroughBumps Next.js-related packages from 15.3.6 → 15.3.8 across several app and package Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
Warning Review ran into problems🔥 ProblemsErrors were encountered while retrieving linked issues. Errors (1)
Comment |
github-actions
bot
added
Dashboard
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #8545 +/- ##
=======================================
Coverage 54.67% 54.67%
=======================================
Files 921 921
Lines 61163 61163
Branches 4153 4153
=======================================
Hits 33439 33439
Misses 27622 27622
Partials 102 102
🚀 New features to boost your workflow:
|
MananTank
force-pushed
the
12-12-update_next.js_version
branch
from
319aa22 to
2c55d38
Compare
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 5
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Disabled knowledge base sources:
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (6)
apps/dashboard/package.json(1 hunks)apps/nebula/package.json(1 hunks)apps/playground-web/package.json(1 hunks)apps/portal/package.json(1 hunks)apps/wallet-ui/package.json(1 hunks)packages/ui/package.json(1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
**/*.{js,jsx,ts,tsx,json}
📄 CodeRabbit inference engine (AGENTS.md)
Biome governs formatting and linting; its rules live in biome.json. Run
pnpm fix&pnpm lintbefore committing, ensure there are no linting errors
Files:
apps/portal/package.jsonapps/dashboard/package.jsonapps/wallet-ui/package.jsonapps/nebula/package.jsonpackages/ui/package.jsonapps/playground-web/package.json
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (8)
- GitHub Check: E2E Tests (pnpm, esbuild)
- GitHub Check: E2E Tests (pnpm, vite)
- GitHub Check: Unit Tests
- GitHub Check: Size
- GitHub Check: Build Packages
- GitHub Check: E2E Tests (pnpm, webpack)
- GitHub Check: Lint Packages
- GitHub Check: Analyze (javascript)
🔇 Additional comments (1)
packages/ui/package.json (1)
28-28: Security patch bump tonext@15.3.8addresses React Server Components vulnerabilities (CVE-2025-55184, CVE-2025-55183, CVE-2025-67779).Appropriate for App Router apps. No other @next/* tooling versions in this manifest to keep in sync.
size-limit report 📦
|
Merge activity
|
<!--
## title your PR with this format: "[SDK/Dashboard/Portal] Feature/Fix: Concise title for the changes"
If you did not copy the branch name from Linear, paste the issue tag here (format is TEAM-0000):
## Notes for the reviewer
Anything important to call out? Be sure to also clarify these in your comments.
## How to test
Unit tests, playground, etc.
-->
<!-- start pr-codex -->
---
## PR-Codex overview
This PR primarily updates various dependencies across multiple `package.json` files, particularly upgrading the `next` version from `15.3.6` to `15.3.8` and `@next/eslint-plugin-next` from `15.3.6` to `15.3.8`. It also modifies the `pnpm-lock.yaml` to reflect these updates.
### Detailed summary
- Updated `next` from `15.3.6` to `15.3.8` in:
- `packages/ui/package.json`
- `apps/wallet-ui/package.json`
- `apps/portal/package.json`
- `apps/playground-web/package.json`
- `apps/nebula/package.json`
- `apps/dashboard/package.json`
- Updated `@next/eslint-plugin-next` from `15.3.6` to `15.3.8` in:
- `apps/wallet-ui/package.json`
- `apps/nebula/package.json`
- `apps/dashboard/package.json`
- Updated `@next/mdx` from `15.3.6` to `15.3.8` in `apps/portal/package.json`.
- Adjusted `pnpm-lock.yaml` to reflect the above dependency updates.
> The following files were skipped due to too many changes: `pnpm-lock.yaml`
> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`
<!-- end pr-codex -->
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
## Summary by CodeRabbit
* **Chores**
* Bumped Next.js and related Next packages (minor/patch updates) across multiple apps and packages for stability and consistency.
* Normalized package manifest formatting across projects; no functional or public API changes introduced.
<sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub>
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
graphite-app
bot
force-pushed
the
12-12-update_next.js_version
branch
from
2c55d38 to
d365efe
Compare
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
apps/dashboard/package.json (1)
55-113: Consider movingprettiertodevDependencies(if not required at runtime).
Keeping it in"dependencies"increases the runtime install surface for the app; if it’s only used by tooling,devDependenciesis the more typical placement.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Disabled knowledge base sources:
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (6)
apps/dashboard/package.json(1 hunks)apps/nebula/package.json(1 hunks)apps/playground-web/package.json(1 hunks)apps/portal/package.json(3 hunks)apps/wallet-ui/package.json(2 hunks)packages/ui/package.json(1 hunks)
🚧 Files skipped from review as they are similar to previous changes (5)
- packages/ui/package.json
- apps/wallet-ui/package.json
- apps/nebula/package.json
- apps/portal/package.json
- apps/playground-web/package.json
🧰 Additional context used
📓 Path-based instructions (1)
**/*.{js,jsx,ts,tsx,json}
📄 CodeRabbit inference engine (AGENTS.md)
Biome governs formatting and linting; its rules live in biome.json. Run
pnpm fix&pnpm lintbefore committing, ensure there are no linting errors
Files:
apps/dashboard/package.json
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (8)
- GitHub Check: Unit Tests
- GitHub Check: E2E Tests (pnpm, webpack)
- GitHub Check: E2E Tests (pnpm, esbuild)
- GitHub Check: Size
- GitHub Check: Lint Packages
- GitHub Check: E2E Tests (pnpm, vite)
- GitHub Check: Build Packages
- GitHub Check: Analyze (javascript)
🔇 Additional comments (3)
apps/dashboard/package.json (3)
2-113: Next.js + @next/ patch versions are aligned (15.3.8).*
This matches the intended coordinated upgrade across Next-related tooling.
1-132: Please ensure repo-levelpnpm fix/pnpm lintis clean after manifest changes.
Biome governs JSON formatting/linting here; worth double-checking CI parity.
119-125: The bundle analyzer is correctly gated and cannot be accidentally enabled during dev. Thenext.config.tsfile loadswithBundleAnalyzeronly whenNODE_ENV === "production"(line 226), and even then, it requiresprocess.env.ANALYZE === "true"(line 229). Since"dev": "next dev --turbopack"runs in development mode and does not set theANALYZEvariable, the analyzer will not be active during normal development. The"build:analyze"script correctly setsANALYZE=truebefore building, allowing the analyzer to run only in that specific context.
PR-Codex overview
This PR focuses on updating various dependencies across multiple
package.jsonfiles, primarily upgrading thenextversion from15.3.6to15.3.8, and updating@next/eslint-plugin-nextand@next/mdxto their latest versions.Detailed summary
nextfrom15.3.6to15.3.8in:packages/ui/package.jsonapps/wallet-ui/package.jsonapps/portal/package.jsonapps/playground-web/package.jsonapps/nebula/package.jsonapps/dashboard/package.json@next/eslint-plugin-nextfrom15.3.6to15.3.8in:apps/wallet-ui/package.jsonapps/playground-web/package.jsonapps/nebula/package.jsonapps/dashboard/package.json@next/mdxfrom15.3.6to15.3.8inapps/portal/package.jsonpnpm-lock.yamlto reflect the changes in dependency versions.Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.