Skip to content

Update dependencies (to fix security vulnerabilities) #6422

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

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update dependencies (to fix security vulnerabilities) #6422

wants to merge 1 commit into from

Conversation

rasmuserik
Copy link
Contributor

@rasmuserik rasmuserik commented Apr 2, 2025 •
edited by coderabbitai bot
Loading

πŸ’» ε˜ζ›΄η±»εž‹ | Change Type

  • feat
  • fix
  • refactor
  • perf
  • style
  • test
  • docs
  • ci
  • chore
  • build

πŸ”€ ε˜ζ›΄θ―΄ζ˜Ž | Description of Change

Update dependencies to fix security bugs etc.

πŸ“ θ‘₯充俑息 | Additional Information

Summary by CodeRabbit

  • Chores
    • Upgraded several core dependencies, including the main framework and visualization tools, to their latest stable versions for improved performance and compatibility.
    • Rolled back one utility dependency to enhance overall stability.

@vercel Vercel
Copy link

vercel bot commented Apr 2, 2025

@rasmuserik is attempting to deploy a commit to the NextChat Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai coderabbitai
Copy link
Contributor

coderabbitai bot commented Apr 2, 2025 •
edited
Loading

Walkthrough

This pull request updates dependency versions in the package.json file. Specifically, it upgrades the versions of @next/third-parties, mermaid, and next to their new major releases, while downgrading the watch package to an earlier version. These changes standardize and align the dependency versions without introducing new features or changing control flow.

Changes

File Change Summary
package.json Upgraded: @next/third-parties (^14.1.0 β†’ ^15.2.4), mermaid (^10.6.1 β†’ ^11.6.0), next (^14.1.1 β†’ ^15.2.4); Downgraded: watch (^1.0.2 β†’ ^0.13.0)

Poem

I'm a rabbit hopping through code so light,
Dependencies updated β€” what a delightful sight!
Upgraded versions dance in the digital glen,
While an older watch hops back again.
In ASCII fields and emoji trails, I cheer with glee,
Celebrating smooth changes for all to see!
πŸ‡πŸ’»πŸŒŸ

πŸ“œ Recent review details

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

πŸ“₯ Commits

Reviewing files that changed from the base of the PR and between 48469bd and ca3cb84.

β›” Files ignored due to path filters (1)
  • yarn.lock is excluded by !**/yarn.lock, !**/*.lock
πŸ“’ Files selected for processing (1)
  • package.json (3 hunks)
πŸ”‡ Additional comments (4)
package.json (4)

27-27: Upgrade @next/third-parties Dependency:
The version has been updated from ^14.1.0 to ^15.2.4. Since this is a major version bump, please verify that the package’s breaking changes (if any) have been considered and that its integration with Next.js and related tooling remains smooth.

40-40: Upgrade Mermaid Dependency:
The version updated from ^10.6.1 to ^11.6.0 is a major upgrade. Ensure that any usage of mermaid in generated diagrams or integrations is tested against the new API changes and that any noted breaking changes are addressed per mermaid's release notes.

42-42: Upgrade Next.js Dependency:
Next.js has been upgraded from ^14.1.1 to ^15.2.4, which is a significant jump. Major version updates can involve configuration changes and breaking API adjustments; please confirm that all Next.js settings, customizations, and runtime behaviors are compatible with the new version.

90-90: Downgrade Watch Package:
The watch package has been downgraded from ^1.0.2 to ^0.13.0. Verify that this older version still meets all current development needs and no required features (or security fixes) have been lost with this downgrade.

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
πŸͺ§ 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.

@rasmuserik rasmuserik mentioned this pull request Apr 8, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@rasmuserik