[Snyk] Upgrade react-router-dom from 6.28.1 to 7.1.1

[guibranco]

User description

Snyk has created this PR to upgrade react-router-dom from 6.28.1 to 7.1.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

⚠️ Warning: This PR contains major version upgrade(s), and may be a breaking change.

• The recommended version is 16 versions ahead of your current version.

• The recommended version was released 21 days ago.

Release notes

Package name: react-router-dom

• 7.1.1 - 2024-12-23
  

  [email protected]

• 7.1.1-pre.0 - 2024-12-21
• 7.1.0 - 2024-12-20
• 7.1.0-pre.0 - 2024-12-18
• 7.0.2 - 2024-12-03
• 7.0.2-pre.0 - 2024-12-02
• 7.0.1 - 2024-11-22
• 7.0.1-pre.0 - 2024-11-22
• 7.0.0 - 2024-11-22
• 7.0.0-pre.6 - 2024-11-19
• 7.0.0-pre.5 - 2024-11-05
• 7.0.0-pre.4 - 2024-10-29
• 7.0.0-pre.3 - 2024-10-29
• 7.0.0-pre.2 - 2024-10-23
• 7.0.0-pre.1 - 2024-10-11
• 7.0.0-pre.0 - 2024-10-03
• 6.28.1 - 2024-12-20

from react-router-dom GitHub release notes

---

Important

• Warning: This PR contains a major version upgrade, and may be a breaking change.
• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Note

I'm currently writing a description for your pull request. I should be done shortly (<1 minute). Please don't edit the description field until I'm finished, or we may overwrite each other. If I find nothing to write about, I'll delete this message.

---

Description

• Major upgrade of react-router-dom to version 7.1.1, which may introduce breaking changes.
• Updated related dependencies and adjusted engine requirements for compatibility.
• This upgrade enhances the project's dependency management and security posture.

---

Changes walkthrough 📝

Relevant files

Enhancement

package-lock.json Upgrade react-router-dom and related dependencies                package-lock.json Upgraded react-router-dom from version 6.28.1 to 7.1.1. Updated react-router dependency to version 7.1.1. Adjusted node engine requirement to >=20.0.0. Added new dependencies: @types/cookie, cookie, set-cookie-parser, and turbo-stream. +50/-24  package.json Update react-router-dom version in package.json                    package.json Updated react-router-dom version from 6.28.1 to 7.1.1. Adjusted node engine requirement to >=20.0.0. +1/-1

---

💡 Penify usage:
Comment /help on the PR to get a list of all available Penify tools and their descriptions

[code-genius-code-coverage]

The files' contents are under analysis for test generation.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request upgrades react-router-dom from version 6.28.1 to 7.1.1. This is a major version upgrade, so it has the potential to introduce breaking changes.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Upgrade react-router-dom	Updated the react-router-dom dependency version from 6.28.1 to 7.1.1 in package.json. Updated package-lock.json to reflect the changes in package.json and include updated dependency information for react-router-dom and its dependencies.	package.json package-lock.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 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. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @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.

[sourcery-ai]

We have skipped reviewing this pull request. It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!

[korbit-ai]

I've completed my review and didn't find any issues.

Need a new review? Comment /korbit-review on this PR and I'll review your latest changes.

Korbit Guide: Usage and Customization

Interacting with Korbit

• You can manually ask Korbit to review your PR using the /korbit-review command in a comment at the root of your PR.
• You can ask Korbit to generate a new PR description using the /korbit-generate-pr-description command in any comment on your PR.
• Too many Korbit comments? I can resolve all my comment threads if you use the /korbit-resolve command in any comment on your PR.
• Chat with Korbit on issues we post by tagging @korbit-ai in your reply.
• Help train Korbit to improve your reviews by giving a 👍 or 👎 on the comments Korbit posts.

Customizing Korbit

• Check out our docs on how you can make Korbit work best for you and your team.
• Customize Korbit for your organization through the Korbit Console.

Current Korbit Configuration

General Settings

​

Setting	Value
Review Schedule	Automatic excluding drafts
Max Issue Count	10
Automatic PR Descriptions	✅

Issue Categories

​

Category	Enabled
Naming	✅
Database Operations	✅
Documentation	✅
Logging	✅
Error Handling	✅
Systems and Environment	✅
Objects and Data Structures	✅
Readability and Maintainability	✅
Asynchronous Processing	✅
Design Patterns	✅
Third-Party Libraries	✅
Performance	✅
Security	✅
Functionality	✅

Feedback and Support

• Tell us what you think of Korbit
• Schedule a call with our team
• Email us @ [email protected]

Note

Korbit Pro is free for open source projects 🎉

Looking to add Korbit to your team? Get started with a free 2 week trial here

[penify-dev]

PR Review 🔍

⏱️ Estimated effort to review [1-5]	2, because the changes are primarily version upgrades in the package-lock.json and package.json files, which are straightforward to review.
🧪 Relevant tests	No
⚡ Possible issues	Breaking Change: Upgrading from react-router-dom 6.x to 7.x may introduce breaking changes that could affect existing routes and components. Ensure to review the migration guide for any necessary code updates.
🔒 Security concerns	No

[penify-dev]

PR Code Suggestions ✨

Category	Suggestion	Score
Compatibility	Verify compatibility of the upgraded package with existing dependencies Ensure that the upgrade to react-router-dom version 7.1.1 is compatible with other dependencies in your project, especially react and react-dom, which are both at version 19.0.0. Check the release notes for react-router-dom to confirm there are no breaking changes that could affect your application. package-lock.json [20] -"react-router-dom": "^7.1.1", +"react-router-dom": "^7.1.1", // Ensure compatibility with other dependencies Suggestion importance[1-10]: 8 Why: This suggestion addresses a crucial aspect of dependency management, ensuring that the upgraded package does not introduce breaking changes.	8
Best practice	Review the new version for deprecated features that may impact your code When upgrading react-router-dom, consider checking for any deprecated features or changes in the API that may require updates in your application code to ensure it functions correctly with the new version. package-lock.json [20] -"react-router-dom": "^7.1.1", +"react-router-dom": "^7.1.1", // Check for deprecated features Suggestion importance[1-10]: 7 Why: This suggestion is important for maintaining code functionality, though it is slightly less critical than ensuring compatibility with other dependencies.	7
Maintainability	Update related packages to maintain compatibility with the new version After upgrading react-router-dom, ensure that all related packages, such as react-router, are also updated to their latest compatible versions to avoid potential conflicts. package.json [16] -"react-router-dom": "^7.1.1", +"react-router-dom": "^7.1.1", // Consider updating related packages Suggestion importance[1-10]: 6 Why: This suggestion promotes maintainability by encouraging the update of related packages, which is a good practice but not as urgent as compatibility checks.	6
Testing	Execute tests to confirm the upgrade does not introduce issues After making these changes, run your tests to ensure that everything is functioning as expected with the new version of react-router-dom and that there are no regressions. package-lock.json [20] -"react-router-dom": "^7.1.1", +"react-router-dom": "^7.1.1", // Run tests after upgrade Suggestion importance[1-10]: 5 Why: While running tests is a standard practice after upgrades, this suggestion is more of a routine check rather than addressing a specific issue or risk.	5

[github-actions]

Infisical secrets check: ✅ No secrets leaked!

💻 Scan logs

4:16AM INF scanning for exposed secrets...
4:16AM INF 451 commits scanned.
4:16AM INF scan completed in 1.13s
4:16AM INF no leaks found