chore(deps): Update dependency @react-router/serve to v8 #69
No reviewers
Labels
No labels
dependencies
major
security-pin
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
trails-cool/trails!69
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/react-router-serve-8.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?
This PR contains the following updates:
^7.18.2→^8.0.0Release Notes
remix-run/react-router (@react-router/serve)
v8.3.0Compare Source
Patch Changes
react-router@8.3.0@react-router/express@8.3.0@react-router/node@8.3.0v8.2.0Compare Source
Patch Changes
react-router@8.2.0@react-router/express@8.2.0@react-router/node@8.2.0v8.1.0Compare Source
Patch Changes
get-portdependency (#15239)react-router@8.1.0@react-router/express@8.1.0@react-router/node@8.1.0v8.0.1Compare Source
Patch Changes
react-router@8.0.1@react-router/express@8.0.1@react-router/node@8.0.1v8.0.0Compare Source
Major Changes
@mjackson/node-fetch-serverto@remix-run/node-fetch-servernow that we can directly use ESM-only packages (#14930)Minor Changes
expressfrom4.21.2to5.2.1Patch Changes
@remix-run/node-fetch-serverfrom^0.13.0to^0.13.3get-portfrom5.1.1to7.2.0react-router@8.0.0@react-router/express@8.0.0@react-router/node@8.0.0Configuration
📅 Schedule: (in timezone Europe/Copenhagen)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate.
9d5d3ad4787ca089003f7ca089003f8182a150e58182a150e5be86597011Superseded by #79, which is merged: main now has react-router and all three adapters at
^8.3.0.These four PRs each bumped one catalog entry to
^8.0.0while leaving the other three at^7.18.2, so every one was a v8 runtime against v7 tooling and none could pass — #71'sTS2305: no exported member 'AppLoadContext'was that split version set, not a migration bug. #79 moved all four together and carried the actual migration (AppLoadContext→RouterContextProvider, metadata→loaderDatain seven routes, dropping the now-defaultv8_middlewareflag).renovate.json5now groups the four packages, placed after the majors →groupName: nullrule so the grouping survives a major — which is when they most need to arrive together. Closing rather than rebasing; the update is already satisfied on main.Pull request closed