chore: Update version for release

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to release-next, this PR will be updated.

Releases

@remix-run/cloudflare@2.11.0

Minor Changes

• Single Fetch: Add a new unstable_data() API as a replacement for json/defer when custom status/headers are needed (#9769)
• Add a new replace(url, init?) alternative to redirect(url, init?) that performs a history.replaceState instead of a history.pushState on client-side navigation redirects (#9764)

Patch Changes

• Updated dependencies:
  • @remix-run/server-runtime@2.11.0

@remix-run/deno@2.11.0

Minor Changes

• Single Fetch: Add a new unstable_data() API as a replacement for json/defer when custom status/headers are needed (#9769)
• Add a new replace(url, init?) alternative to redirect(url, init?) that performs a history.replaceState instead of a history.pushState on client-side navigation redirects (#9764)

Patch Changes

• Updated dependencies:
  • @remix-run/server-runtime@2.11.0

@remix-run/dev@2.11.0

Minor Changes

• Rename future.unstable_fogOfWar to future.unstable_lazyRouteDiscovery for clarity (#9763)

Patch Changes

• Handle absolute Vite base URLs (#9700)
• Updated dependencies:
  • @remix-run/node@2.11.0
  • @remix-run/server-runtime@2.11.0

@remix-run/node@2.11.0

Minor Changes

• Single Fetch: Add a new unstable_data() API as a replacement for json/defer when custom status/headers are needed (#9769)
• Add a new replace(url, init?) alternative to redirect(url, init?) that performs a history.replaceState instead of a history.pushState on client-side navigation redirects (#9764)

Patch Changes

• Updated dependencies:
  • @remix-run/server-runtime@2.11.0

@remix-run/react@2.11.0

Minor Changes

• Single Fetch: Add a new unstable_data() API as a replacement for json/defer when custom status/headers are needed (#9769)

• Add a new replace(url, init?) alternative to redirect(url, init?) that performs a history.replaceState instead of a history.pushState on client-side navigation redirects (#9764)

• Rename future.unstable_fogOfWar to future.unstable_lazyRouteDiscovery for clarity (#9763)

• Single Fetch: Remove responseStub in favor of headers (#9769)

  • Background

    • The original Single Fetch approach was based on an assumption that an eventual middleware implementation would require something like ResponseStub so users could mutate status/headers in middleware before/after handlers as well as during handlers
    • We wanted to align how headers got merged between document and data requests
    • So we made document requests also use ResponseStub and removed the usage of headers in Single Fetch
    • The realization/alignment between Michael and Ryan on the recent roadmap planning made us realize that the original assumption was incorrect
    • middleware won't need a stub - users can just mutate the Response they get from await next() directly
    • With that gone, and still wanting to align how headers get merged, it makes more sense to stick with the current headers API and apply that to Single Fetch and avoid introducing a totally new thing in RepsonseStub (that always felt a bit awkward to work with anyway)

  • With this change:

    • You are encouraged to stop returning Response instances in favor of returning raw data from loaders and actions:
      • return json({ data: whatever });
      • return { data: whatever };
    • In most cases, you can remove your json() and defer() calls in favor of returning raw data if they weren't setting custom status/headers
      • We will be removing both json and defer in the next major version, but both should still work in Single Fetch in v2 to allow for incremental adoption of the new behavior
    • If you need custom status/headers:
      • We've added a new unstable_data({...}, responseInit) utility that will let you send back status/headers alongside your raw data without having to encode it into a Response
    • The headers() function will let you control header merging for both document and data requests

Patch Changes

• Bump to RR stable (#9815)
• Single Fetch: Ensure calls don't include any trailing slash from the pathname (i.e., /path/.data) (#9792)
• [REMOVE] Fix typings for unstable_data and useLoaderData (#9811)
• Single Fetch: Add undefined to the useRouteLoaderData type override (#9796)
• Change initial hydration route mismatch from a URL check to a matches check to be resistant to URL inconsistencies (#9695)
• Updated dependencies:
  • @remix-run/server-runtime@2.11.0

@remix-run/server-runtime@2.11.0

Minor Changes

• Single Fetch: Add a new unstable_data() API as a replacement for json/defer when custom status/headers are needed (#9769)

• Add a new replace(url, init?) alternative to redirect(url, init?) that performs a history.replaceState instead of a history.pushState on client-side navigation redirects (#9764)

• Rename future.unstable_fogOfWar to future.unstable_lazyRouteDiscovery for clarity (#9763)

• Single Fetch: Remove responseStub in favor of headers (#9769)

  • Background

    • The original Single Fetch approach was based on an assumption that an eventual middleware implementation would require something like ResponseStub so users could mutate status/headers in middleware before/after handlers as well as during handlers
    • We wanted to align how headers got merged between document and data requests
    • So we made document requests also use ResponseStub and removed the usage of headers in Single Fetch
    • The realization/alignment between Michael and Ryan on the recent roadmap planning made us realize that the original assumption was incorrect
    • middleware won't need a stub - users can just mutate the Response they get from await next() directly
    • With that gone, and still wanting to align how headers get merged, it makes more sense to stick with the current headers API and apply that to Single Fetch and avoid introducing a totally new thing in RepsonseStub (that always felt a bit awkward to work with anyway)

  • With this change:

    • You are encouraged to stop returning Response instances in favor of returning raw data from loaders and actions:
      • return json({ data: whatever });
      • return { data: whatever };
    • In most cases, you can remove your json() and defer() calls in favor of returning raw data if they weren't setting custom status/headers
      • We will be removing both json and defer in the next major version, but both should still work in Single Fetch in v2 to allow for incremental adoption of the new behavior
    • If you need custom status/headers:
      • We've added a new unstable_data({...}, responseInit) utility that will let you send back status/headers alongside your raw data without having to encode it into a Response
    • The headers() function will let you control header merging for both document and data requests

Patch Changes

• Change initial hydration route mismatch from a URL check to a matches check to be resistant to URL inconsistencies (#9695)

@remix-run/testing@2.11.0

Minor Changes

• Rename future.unstable_fogOfWar to future.unstable_lazyRouteDiscovery for clarity (#9763)

Patch Changes

• Updated dependencies:
  • @remix-run/node@2.11.0
  • @remix-run/react@2.11.0

@remix-run/architect@2.11.0

Patch Changes

• Updated dependencies:
  • @remix-run/node@2.11.0

@remix-run/cloudflare-pages@2.11.0

Patch Changes

• Updated dependencies:
  • @remix-run/cloudflare@2.11.0

@remix-run/cloudflare-workers@2.11.0

Patch Changes

• Updated dependencies:
  • @remix-run/cloudflare@2.11.0

@remix-run/express@2.11.0

Patch Changes

• Updated dependencies:
  • @remix-run/node@2.11.0

@remix-run/serve@2.11.0

Patch Changes

• Updated dependencies:
  • @remix-run/node@2.11.0
  • @remix-run/express@2.11.0

create-remix@2.11.0

remix@2.11.0

remix

See the CHANGELOG.md in individual Remix packages for all changes.

@remix-run/css-bundle@2.11.0

@remix-run/eslint-config@2.11.0