-
Notifications
You must be signed in to change notification settings - Fork 39
fix(deps): update react j:kit-282 #6809
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
Open
renovate-coveo
wants to merge
1
commit into
main
Choose a base branch
from
renovate/react
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
+80
−77
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
85ec7c9 to
6c0cdd0
Compare
Dependency Review✅ No vulnerabilities or license issues found.Scanned Files
|
6c0cdd0 to
4902086
Compare
4902086 to
3d4543d
Compare
3d4543d to
6c36790
Compare
6c36790 to
6869c98
Compare
6869c98 to
c42ce06
Compare
c42ce06 to
6036c31
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.07.10.1->7.11.016.3.0->16.3.15.1.1->5.1.27.10.1->7.11.0Release Notes
remix-run/react-router (@react-router/dev)
v7.11.0Compare Source
Minor Changes
vite previewsupport (#14507)Patch Changes
routeRSCServerRequestreplacefetchServerwithserverResponse(#14597)react-router@7.11.0@react-router/serve@7.11.0@react-router/node@7.11.0remix-run/react-router (@react-router/fs-routes)
v7.11.0Compare Source
Patch Changes
@react-router/dev@7.11.0remix-run/react-router (@react-router/node)
v7.11.0Compare Source
Patch Changes
react-router@7.11.0remix-run/react-router (@react-router/serve)
v7.11.0Compare Source
Patch Changes
compressionandmorgandependencies to addresson-headersCVE: GHSA-76c9-3jph-rj3q (#14652)react-router@7.11.0@react-router/node@7.11.0@react-router/express@7.11.0testing-library/react-testing-library (@testing-library/react)
v16.3.1Compare Source
Bug Fixes
vitejs/vite-plugin-react (@vitejs/plugin-react)
v5.1.2Compare 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)Configuration
📅 Schedule: Branch creation - "before 4:00am on Tuesday" in timezone America/Toronto, Automerge - "after 9:00am and before 12:00pm on tuesday, wednesday, thursday" in timezone America/Toronto.
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, 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 has been generated by Renovate Bot.