-
Notifications
You must be signed in to change notification settings - Fork 106
chore(deps): update all non-major dependencies (examples, templates & patterns) (minor) #8052
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Size Change: -3 B (0%) Total Size: 453 kB
ℹ️ View Unchanged
|
Pull Request Test Coverage Report for Build 20424336981Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
Lukas742
approved these changes
Dec 22, 2025
b85d413 to
58a566c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
7.10.1->7.11.07.10.1->7.11.07.10.1->7.11.015.7.1->15.8.116.0.10->16.1.016.0.10->16.1.07.10.1->7.11.08.49.0->8.50.07.2.7->7.3.0Release Notes
remix-run/react-router (@react-router/dev)
v7.11.0Compare Source
Minor Changes
vite previewsupport (#14507)Patch Changes
routeRSCServerRequestreplacefetchServerwithserverResponse(#14597)[email protected]@react-router/[email protected]@react-router/[email protected]remix-run/react-router (@react-router/node)
v7.11.0Compare Source
Patch Changes
[email protected]remix-run/react-router (@react-router/serve)
v7.11.0Compare Source
Patch Changes
compressionandmorgandependencies to addresson-headersCVE: GHSA-76c9-3jph-rj3q (#14652)[email protected]@react-router/[email protected]@react-router/[email protected]cypress-io/cypress (cypress)
v15.8.1Compare Source
Changelog: https://docs.cypress.io/app/references/changelog#15-8-1
v15.8.0Compare Source
Changelog: https://docs.cypress.io/app/references/changelog#15-8-0
vercel/next.js (eslint-config-next)
v16.1.0Compare Source
vercel/next.js (next)
v16.1.0Compare Source
remix-run/react-router (react-router)
v7.11.0Compare Source
Minor Changes
<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, throwdata()instead. (#14632)Fix
unstable_useTransitionsprop on<Router>component to permit omission for backewards compatibility (#14646)routeRSCServerRequestreplacefetchServerwithserverResponse(#14597)[UNSTABLE] Add a new
unstable_defaultShouldRevalidateflag to various APIs to allow opt-ing out of standard revalidation behaviors. (#14542)If active routes include a
shouldRevalidatefunction, then your value will be passed asdefaultShouldRevalidatein 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
dataStrategyimplementations that return insufficient result sets by adding errors for routes without any available result (#14627)typescript-eslint/typescript-eslint (typescript-eslint)
v8.50.0Compare Source
This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
vitejs/vite (vite)
v7.3.0Compare Source
Please refer to CHANGELOG.md for details.
Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.