From d2f1f1baa5f7f75def8e07bac3c37fb185c04e1f Mon Sep 17 00:00:00 2001 From: rossipedia Date: Mon, 20 Jul 2026 10:24:36 -0600 Subject: [PATCH] update changes files to use h4 instead of h3 (#15334) --- .../.changes/unstable.rsc-subresource-integrity.md | 2 +- packages/react-router/.changes/unstable.rsc-client-version.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/packages/react-router-dev/.changes/unstable.rsc-subresource-integrity.md b/packages/react-router-dev/.changes/unstable.rsc-subresource-integrity.md index 271c6e15d8..01a1047593 100644 --- a/packages/react-router-dev/.changes/unstable.rsc-subresource-integrity.md +++ b/packages/react-router-dev/.changes/unstable.rsc-subresource-integrity.md @@ -1,6 +1,6 @@ Support the `subResourceIntegrity` config option in RSC Framework Mode -### Migration guide +#### Migration guide No changes are required when using the default RSC SSR entry. If you maintain a custom `app/entry.ssr.tsx`, import the new virtual module and pass its hashes to React's `importMap` render option: diff --git a/packages/react-router/.changes/unstable.rsc-client-version.md b/packages/react-router/.changes/unstable.rsc-client-version.md index 596756b0a7..66d652cf88 100644 --- a/packages/react-router/.changes/unstable.rsc-client-version.md +++ b/packages/react-router/.changes/unstable.rsc-client-version.md @@ -1,6 +1,6 @@ Detect stale RSC clients during lazy route discovery and reload the destination document -### Migration +#### Migration Apps using the default RSC Framework entry do not need to make any changes. Apps with a custom `entry.rsc.tsx` should import the generated client version and pass it to `unstable_matchRSCServerRequest`: