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

[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.22.2.

ℹ️ 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 36 versions ahead of your current version.
• The recommended version was released 22 days ago, on 2024-02-28.

Release notes

Package name: react-router-dom

• 6.22.2 - 2024-02-28
  

  react-router-native@6.22.2

• 6.22.2-pre.0 - 2024-02-27
  

  react-router-native@6.22.2-pre.0

• 6.22.1 - 2024-02-16
• 6.22.1-pre.0 - 2024-02-16
• 6.22.0 - 2024-02-01
• 6.22.0-pre.0 - 2024-01-31
• 6.21.3 - 2024-01-18
• 6.21.3-pre.0 - 2024-01-16
• 6.21.2 - 2024-01-11
• 6.21.2-pre.0 - 2024-01-09
• 6.21.1 - 2023-12-21
• 6.21.1-pre.0 - 2023-12-21
• 6.21.0 - 2023-12-13
• 6.21.0-pre.3 - 2023-12-06
• 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

• 78c843b chore: Update version for release (#11314)
• 8f52cd2 Exit prerelease mode
• cd2f69d Update release date
• e6b9e3b Draft release notes
• e1421be chore: Update version for release (pre) (#11309)
• eec4ca9 Enter prerelease mode
• 7f93b4b Merge branch 'main' into release-next
• 95acd38 Merge branch 'release-next' into dev
• 74f8676 Merge branch 'release-next'
• 6b22f91 Preserve hydrated errors during partial hydration (#11305)
• 13ac1b6 chore: sort contributors list
• 56fbdb2 Update context provider link to point to React's new documentation site (#11290)
• 5f0cf32 chore: Update version for release (#11283)
• 671a966 Exit prerelease mode
• 25d16db chore: Update version for release (pre) (#11280)
• 24685c9 Enter prerelease mode
• b7e9836 Merge branch 'main' into release-next
• c164837 chore: sort contributors list
• 5d475a2 fix typo in faq.md (#11272)
• 9aed7d0 docs: listen for close event on response, not request (#11249)
• 135e8aa Add note on relative:path starting point
• 9f36087 Fix typo in loader.md (#11256)
• 362115a Update CI to node 20 and fix issue with build on experimental releases (#11257)
• 241f2d4 Fix issues with pre-encoded param names not being properly decoded (#11199)

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.