[Snyk] Upgrade react-router-dom from 6.14.2 to 6.21.0

[tural-xanaliyev]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to upgrade react-router-dom from 6.14.2 to 6.21.0.

ℹ️ 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.

---

• The recommended version is 24 versions ahead of your current version.
• The recommended version was released 22 days ago, on 2023-12-13.

Release notes

Package name: react-router-dom

• 6.21.0 - 2023-12-13
  

  react-router-native@6.21.0

• 6.21.0-pre.3 - 2023-12-06
  

  react-router-native@6.21.0-pre.3

• 6.21.0-pre.2 - 2023-12-05
• 6.21.0-pre.1 - 2023-12-05
• 6.21.0-pre.0 - 2023-12-05
• 6.20.1 - 2023-12-01
• 6.20.1-pre.0 - 2023-12-01
• 6.20.0 - 2023-11-22
• 6.20.0-pre.0 - 2023-11-21
• 6.19.0 - 2023-11-16
• 6.19.0-pre.0 - 2023-11-14
• 6.18.0 - 2023-10-31
• 6.18.0-pre.1 - 2023-10-30
• 6.18.0-pre.0 - 2023-10-26
• 6.17.0 - 2023-10-16
• 6.17.0-pre.2 - 2023-10-13
• 6.17.0-pre.1 - 2023-10-12
• 6.17.0-pre.0 - 2023-10-11
• 6.16.0 - 2023-09-13
• 6.16.0-pre.2 - 2023-09-06
• 6.16.0-pre.1 - 2023-09-05
• 6.16.0-pre.0 - 2023-08-28
• 6.15.0 - 2023-08-10
• 6.15.0-pre.0 - 2023-08-09
• 6.14.2 - 2023-07-17

from react-router-dom GitHub release notes

Commit messages

Package name: react-router-dom

• 69ba50e chore: Update version for release (#11114)
• ffd4373 Exit prerelease mode
• ea0ffee chore: Update version for release (pre) (#11095)
• fe3c071 Slight refactor to partial hydration to leverage state.initialized properly (#11094)
• ed40ee9 Update release notes comparison link
• 1447eb0 Update release notes
• 373b30c chore: Update version for release (pre) (#11091)
• f9d7ed6 Fix server future plumbing
• 56b2944 chore: Update version for release (pre) (#11090)
• 558d793 Fix plumbing of future prop
• 1c6f3b3 fix typos
• ee5fcd5 Generate release notes
• ddc2b94 chore: Update version for release (pre) (#11089)
• 1752d84 Enter prerelease mode
• 120de8c Merge branch 'main' into release-next
• 149ad65 Add future.v7_relativeSplatPath flag (#11087)
• 839df23 Bump bundle
• d04c541 Fix tests from conflicting PRs
• 0d2a38c Support partial hydration for Remix clientLoader/clientAction (#11033)
• cb53f41 Fix issue when rendering Link/NavLink outside of matched routes (#11062)
• 211c1ff Bump bundle
• e6814d5 Properly handle falsy error values in ErrorBoundary's (#11071)
• dc7833c Catch errors when trying to unwrap responses (#11061)
• 7a5c0a7 Merge branch 'release-next' into dev

Compare

---

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

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[pull-request-quantifier-deprecated]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 2

Change summary by file extension:
.json : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.