chore(wren-ui): Upgrade the Next.js version to 14.2.26

[fredalai]

Description

• Upgrade the Next.js package version from 14.2.21 to 14.2.26.

The WrenAI is not affected by this vulnerability, but the package should still be upgraded accordingly.

Ref:

• https://nextjs.org/blog/cve-2025-29927
• Next.js
  • https://github.com/vercel/next.js/releases/tag/v14.2.25
  • https://github.com/vercel/next.js/releases/tag/v14.2.26

Summary by CodeRabbit

• Chores
  • Upgraded the Next.js framework to the latest version, potentially enhancing performance, stability, and overall experience.

[coderabbitai]

Walkthrough

The pull request updates the Next.js dependency in the wren-ui/package.json file. The version is changed from "14.2.21" to "14.2.26", reflecting an upgrade likely containing bug fixes, performance improvements, or new features provided by the framework update. This change affects only the dependency version without any alterations to other configurations.

Changes

File	Change Summary
wren-ui/package.json	Updated Next.js version from "14.2.21" to "14.2.26".

Possibly related PRs

• chore(wren-ui): update eslint-config-next version to 14.2.21 #1087: Updates ESLint configuration for Next.js to ensure compatibility with the framework update.
• chore(wren-ui): update Next.js dependency to version 14.2.15 #1083: Also modifies the Next.js dependency, updating it to version 14.2.15, and is directly related to dependency management.

Suggested labels

module/ui

Suggested reviewers

• andreashimin

Poem

I’m a rabbit, quick and keen,
Hopping through code, neat and clean.
Next.js updated with a twitch,
Bugs and issues, now be ditched!
With each upgrade, we celebrate –
A happy leap towards a better state!
🐇✨

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

wren-ui/package.json (1)

70-70: DevDependency Version Consistency Check
While the core Next.js framework has been upgraded, the "eslint-config-next" package remains at "14.2.21". To maintain consistency and potentially benefit from updated linting rules aligned with the new Next.js version, consider upgrading "eslint-config-next" to "14.2.26" (if compatible with your project's setup).

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9fbd592 and 961df34.

⛔ Files ignored due to path filters (1)

• wren-ui/yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (1)

• wren-ui/package.json (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: Analyze (javascript-typescript)
• GitHub Check: Analyze (go)

🔇 Additional comments (1)

wren-ui/package.json (1)

31-31: Next.js Dependency Upgrade Applied Correctly
The Next.js version in the dependencies has been updated from "14.2.21" to "14.2.26" as intended. Please verify that this version fully addresses the referenced vulnerability (CVE-2025-29927) and that any breaking changes in Next.js 14.2.26 have been tested in the application.