pierre/MatrixGW
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases 2 Wiki Activity

Update dependency react-router to ^7.11.0 #142

Merged
renovate merged 1 commits from renovate/react-router-7.x into master 2025-12-30 00:32:16 +00:00
Conversation 0 Commits 1 Files Changed 2 +5 -5
renovate commented 2025-12-30 00:32:08 +00:00
Collaborator
Copy Link

This PR contains the following updates:

Package Type Update Change
react-router (source) dependencies minor ^7.10.1 → ^7.11.0

Release Notes

remix-run/react-router (react-router)

v7.11.0

Compare Source

Minor Changes
  • Stabilize <HydratedRouter onError>/<RouterProvider onError> (#​14546)
Patch Changes

  • add support for throwing redirect Response's at RSC render time (#​14596)

  • Support for throwing data() and Response from server component render phase. Response body is not serialized as async work is not allowed as error encoding phase. If you wish to transmit data to the boundary, throw data() instead. (#​14632)

  • Fix unstable_useTransitions prop on <Router> component to permit omission for backewards compatibility (#​14646)

  • routeRSCServerRequest replace fetchServer with serverResponse (#​14597)

  • [UNSTABLE] Add a new unstable_defaultShouldRevalidate flag to various APIs to allow opt-ing out of standard revalidation behaviors. (#​14542)

    If active routes include a shouldRevalidate function, then your value will be passed as defaultShouldRevalidate in those function so that the route always has the final revalidation determination.

    • <Form method="post" unstable_defaultShouldRevalidate={false}>
    • submit(data, { method: "post", unstable_defaultShouldRevalidate: false })
    • <fetcher.Form method="post" unstable_defaultShouldRevalidate={false}>
    • fetcher.submit(data, { method: "post", unstable_defaultShouldRevalidate: false })

    This is also available on non-submission APIs that may trigger revalidations due to changing search params:

    • <Link to="/" unstable_defaultShouldRevalidate={false}>
    • navigate("/?foo=bar", { unstable_defaultShouldRevalidate: false })
    • setSearchParams(params, { unstable_defaultShouldRevalidate: false })

  • Allow redirects to be returned from client side middleware (#​14598)

  • Handle dataStrategy implementations that return insufficient result sets by adding errors for routes without any available result (#​14627)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [react-router](https://github.com/remix-run/react-router) ([source](https://github.com/remix-run/react-router/tree/HEAD/packages/react-router)) | dependencies | minor | [`^7.10.1` → `^7.11.0`](https://renovatebot.com/diffs/npm/react-router/7.10.1/7.11.0) | --- ### Release Notes <details> <summary>remix-run/react-router (react-router)</summary> ### [`v7.11.0`](https://github.com/remix-run/react-router/blob/HEAD/packages/react-router/CHANGELOG.md#7110) [Compare Source](https://github.com/remix-run/react-router/compare/react-router@7.10.1...react-router@7.11.0) ##### Minor Changes - Stabilize `<HydratedRouter onError>`/`<RouterProvider onError>` ([#&#8203;14546](https://github.com/remix-run/react-router/pull/14546)) ##### Patch Changes - add support for throwing redirect Response's at RSC render time ([#&#8203;14596](https://github.com/remix-run/react-router/pull/14596)) - Support for throwing `data()` and Response from server component render phase. Response body is not serialized as async work is not allowed as error encoding phase. If you wish to transmit data to the boundary, throw `data()` instead. ([#&#8203;14632](https://github.com/remix-run/react-router/pull/14632)) - Fix `unstable_useTransitions` prop on `<Router>` component to permit omission for backewards compatibility ([#&#8203;14646](https://github.com/remix-run/react-router/pull/14646)) - `routeRSCServerRequest` replace `fetchServer` with `serverResponse` ([#&#8203;14597](https://github.com/remix-run/react-router/pull/14597)) - \[UNSTABLE] Add a new `unstable_defaultShouldRevalidate` flag to various APIs to allow opt-ing out of standard revalidation behaviors. ([#&#8203;14542](https://github.com/remix-run/react-router/pull/14542)) If active routes include a `shouldRevalidate` function, then your value will be passed as `defaultShouldRevalidate` in those function so that the route always has the final revalidation determination. - `<Form method="post" unstable_defaultShouldRevalidate={false}>` - `submit(data, { method: "post", unstable_defaultShouldRevalidate: false })` - `<fetcher.Form method="post" unstable_defaultShouldRevalidate={false}>` - `fetcher.submit(data, { method: "post", unstable_defaultShouldRevalidate: false })` This is also available on non-submission APIs that may trigger revalidations due to changing search params: - `<Link to="/" unstable_defaultShouldRevalidate={false}>` - `navigate("/?foo=bar", { unstable_defaultShouldRevalidate: false })` - `setSearchParams(params, { unstable_defaultShouldRevalidate: false })` - Allow redirects to be returned from client side middleware ([#&#8203;14598](https://github.com/remix-run/react-router/pull/14598)) - Handle `dataStrategy` implementations that return insufficient result sets by adding errors for routes without any available result ([#&#8203;14627](https://github.com/remix-run/react-router/pull/14627)) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0Mi42Ni4xNCIsInVwZGF0ZWRJblZlciI6IjQyLjY2LjE0IiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIiwibGFiZWxzIjpbXX0=-->
renovate added 1 commit 2025-12-30 00:32:10 +00:00
Update dependency react-router to ^7.11.0
All checks were successful
continuous-integration/drone/push Build is passing
Details
continuous-integration/drone/pr Build is passing
Details
9da2a9e9b3
renovate scheduled this pull request to auto merge when all checks succeed 2025-12-30 00:32:12 +00:00
renovate merged commit 2aaced17d8 into master 2025-12-30 00:32:16 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
renovate pierre
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: pierre/MatrixGW#142
Delete Branch "renovate/react-router-7.x"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?