chore(deps): bump react-router-dom from 7.12.0 to 7.13.0 in /apps/frontend

[dependabot]

Bumps react-router-dom from 7.12.0 to 7.13.0.

Release notes

Sourced from react-router-dom's releases.

react-router-dom-v5-compat@6.4.0-pre.15

Patch Changes

• Updated dependencies
  • react-router@6.4.0-pre.15
  • react-router-dom@6.4.0-pre.15

Changelog

Sourced from react-router-dom's changelog.

7.13.0

Patch Changes

• Updated dependencies:
  • react-router@7.13.0

Commits

• 5557ba3 chore: Update version for release (#14749)
• 62c6e0e chore: Update version for release (pre) (#14738)
• See full diff in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[fingertips18]

@coderabbitai Are there any breaking changes in this dependency update? Is it safe to merge?

[coderabbitai]

Important

Review skipped

Bot user detected.

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.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🌐 Web query:

react-router-dom 7.13.0 release notes breaking changes

💡 Result:

react-router-dom / react-router v7.13.0 release notes (breaking changes?)

No explicit breaking changes are listed for v7.13.0—it’s a minor + patch release. The published notes include: [1]

Minor

• Add crossOrigin prop to the Links component. [1]

Patches / behavior changes (could be “breaking” if you depended on old behavior)

• Failed origin checks now return HTTP 400 instead of 500. [1]
• Loosen allowedActionOrigins glob matching so ** matches all domains. [1]
• Fixes: double-slash normalization for useNavigate paths with :, missing nonce on inline criticalCss, and route file path handling when the routes dir is outside the app dir. [1]

Note about react-router-dom in v7

• react-router-dom is effectively a compatibility package that re-exports from react-router (and is deprecated for v7+ imports). [2]

Sources: [1] [2]

---

@fingertips18, based on the release notes for react-router-dom 7.13.0, there are no explicit breaking changes listed. This is a minor version update that should be backward compatible. ✅

Key changes in 7.13.0:

Minor additions:

• New crossOrigin prop added to the Links component

Patches/fixes:

• Failed origin checks now return HTTP 400 instead of 500 (bug fix)
• Improved allowedActionOrigins glob matching (** now matches all domains)
• Fixes for double-slash normalization, missing nonce on inline criticalCss, and route file path handling

Safety assessment:

The update is generally safe to merge. However, be aware of these edge cases:

• If your error handling specifically checks for HTTP 500 status codes from origin validation failures, you'll now receive 400 instead
• If you use allowedActionOrigins with glob patterns, the looser matching behavior might affect your configuration

Recommendation: The update is safe for most applications. I'd suggest running your test suite to ensure nothing breaks, especially if you have custom error handling around origin checks or use origin-related configurations.