This repository has been archived by the owner on Feb 17, 2025. It is now read-only.
chore(deps): update remix monorepo to v2.13.1 #129
Merged
Conversation
This file contains 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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
![renovate-approve[bot]](https://avatars.githubusercontent.com/in/7394?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/remix-monorepo
branch
from
13e727c to
c9c916b
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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:
2.12.1->2.13.12.12.1->2.13.12.12.1->2.13.12.12.1->2.13.1Release Notes
remix-run/remix (@remix-run/dev)
v2.13.1Compare Source
Patch Changes
future.v3_optimizeDepsback tofuture.unstable_optimizeDepsas it was not intended to stabilize in Remix v2 (#10099)@remix-run/[email protected]@remix-run/[email protected]v2.13.0Compare Source
Minor Changes
future.unstable_optimizeDepsflag intofuture.v3_optimizeDeps(#10092)unstable_dataStrategy->dataStrategyunstable_patchRoutesOnNavigation->patchRoutesOnNavigationunstable_data()->data()unstable_viewTransition->viewTransition(Link,Form,navigate,submit)unstable_flushSync>-><Link viewTransition>(Link,Form,navigate,submit,useFetcher)future.unstable_singleFetch->future.v3_singleFetchfuture.unstable_lazyRouteDiscovery->future.v3_lazyRouteDiscoveryPatch Changes
Stop passing
request.signalas therenderToReadableStreamsignalto abort server rendering for cloudflare/deno runtimes because by the time thatrequestis aborted, aborting the rendering is useless because there's no way for React to flush down the unresolved boundaries (#10047)remix vite:devbecause we were incorrectly aborting requests after successful renders - which was causing us to abort a completed React render, and try to close an already closedReadableStream.request.signalon successful rendersentry.serverfiles no longer pass asignaltorenderToReadableStreambecause adding a timeout-based abort signal to the default behavior would constitute a breaking changeentry.serverviaremix reveal entry.server, and the template entry.server files have been updated with an example approach for newly created Remix appsFix adapter logic for aborting
request.signalso we don't incorrectly abort on thecloseevent for successful requests (#10046)Updated dependencies:
@remix-run/[email protected]@remix-run/[email protected]remix-run/remix (@remix-run/node)
v2.13.1Compare Source
Patch Changes
@remix-run/[email protected]v2.13.0Compare Source
Patch Changes
@remix-run/[email protected]remix-run/remix (@remix-run/react)
v2.13.1Compare Source
Patch Changes
@remix-run/[email protected]v2.13.0Compare Source
Minor Changes
unstable_dataStrategy->dataStrategyunstable_patchRoutesOnNavigation->patchRoutesOnNavigationunstable_data()->data()unstable_viewTransition->viewTransition(Link,Form,navigate,submit)unstable_flushSync>-><Link viewTransition>(Link,Form,navigate,submit,useFetcher)future.unstable_singleFetch->future.v3_singleFetchfuture.unstable_lazyRouteDiscovery->future.v3_lazyRouteDiscoveryPatch Changes
clientLoader.hydratein a layout route when hydrating with bubbled errors (#10063)@remix-run/[email protected]remix-run/remix (@remix-run/serve)
v2.13.1Compare Source
Patch Changes
@remix-run/[email protected]@remix-run/[email protected]v2.13.0Compare Source
Patch Changes
@remix-run/[email protected]@remix-run/[email protected]Configuration
📅 Schedule: Branch creation - "before 3am" in timezone Asia/Tokyo, 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 these updates again.
This PR was generated by Mend Renovate. View the repository job log.