• Turbopack: bump trace format header to TRACEv1: #99781
• Pass staged fallback params directly to adapter renders: #100456
• Fix navigation from global-not-found to app routes: #100592
• End the cache-signal read when encryptActionBoundArgs hits the RDC: #100622
• Ignore flaky turbo-tasks-fs watcher tests in CI: #100627

• test: enable build-error suites in deploy mode: #100482
• test: enable deploy-excluded suites verified against deployments: #100484
• Turbopack: fix trace crates after concurrent trace format changes: #100656
• [cd] Document that Turbopack team can also approve releases: #100650
• Turbopack: delta-encode trace timestamps: #99809
• docs: add turbo_tasks development guidance for agents: #100581
• Fix pnpm new-test unit type generating no test file: #100641
• [test] Reproduce two cache-sharing bugs: #100510
• [test] Cover cache sharing after handler failures: #100519

Huge thanks to @jamiboym, @sokra, @eps1lon, @mischnic, @unstubbable, @kassens, @huozhi, and @digasic for helping!

• allow percent sign in raw argument type (#4307) (6971e5c)

• Bumped @remix-run/* dependencies:
  • component@1.1.0
  • render-middleware@1.0.1

• BREAKING CHANGE: Prop types for the previously removed styled Accordion, Select, and Combobox components have also been removed: AccordionProps, AccordionItemProps, AccordionTriggerProps, AccordionContentProps, SelectProps, SelectOptionProps, ComboboxProps, and ComboboxOptionProps. Accordion's unused headingLevel prop and corresponding context fields, along with the AccordionHeadingLevel type, have also been removed. (#11986)

• BREAKING CHANGE: The toggle mixin is now exported as toggle instead of control. Since toggle consists of a single mixin, it can now be called directly as toggle() rather than grouped under toggle.control(). (#11986)

  -import * as toggle from '@remix-run/ui/toggle'
  +import { toggle } from '@remix-run/ui/toggle'
  
  -<input mix={toggle.control({ defaultChecked: true })} />
  +<input mix={toggle({ defaultChecked: true })} />

  The options type has also been renamed from ToggleControlOptions to ToggleOptions:

  -import type { ToggleControlOptions } from '@remix-run/ui/toggle'
  +import type { ToggleOptions } from '@remix-run/ui/toggle'

• Check the user's current motion preference with prefersReducedMotion() from @remix-run/ui/animation. It returns false during server rendering or when matchMedia is unavailable, so it can be called safely from component render functions as well as browser event handlers. (#11993)

  import { animateLayout, prefersReducedMotion, spring } from '@remix-run/ui/animation'
  
  function Card() {
    return () => (
      <div mix={animateLayout(prefersReducedMotion() ? false : { ...spring('snappy') })}>Details</div>
    )
  }

• Server rendering skips setup and render for animation mixins, keyboard and outside-click helpers, typeahead behavior, and popover anchor and focus helpers. Mixins that provide initial attributes, styles, or ARIA props still run on the server. (#12019)

• Bumped @remix-run/* dependencies:

  • component@1.1.0

• Bumped @remix-run/* dependencies:
  • assets@1.0.1
  • component@1.1.0
  • response@1.0.1

• Stop parsing entries after the standard two-zero-block tar end marker while continuing to enforce the total archive size limit on trailing input (see #12035). (#12041)

• createFileResponse() now ignores valid range requests on empty files and returns 416 Range Not Satisfiable for zero-length suffix ranges on nonempty files, avoiding invalid partial responses. (#12043)

• Reduce memory use when streaming HTML by checking a short prefix for a doctype instead of decoding the whole first chunk. Leading whitespace and declarations that cross the prefix boundary continue to work. (#12016)

• createFileResponse() now ignores unsupported Range units and returns the full file instead of interpreting those ranges as byte ranges. (#12045)

• Bumped @remix-run/* dependencies:

  • headers@1.0.1

• Mixins created through remix/component can use createMixin(setup, { ssr: false }) to skip setup and render on the server while keeping browser behavior and hydration. Server rendering remains enabled by default. The option is intended for behavior that does not contribute to the server HTML. (#12019)

• Server rendering with remix/component is about twice as fast as in 3.0 and uses less memory, with no code changes. Rendering a 48-product listing page with renderToString() takes 244 µs instead of 513 µs (Node.js 24.18 on an Apple M5 Pro, median of 5 fresh-process runs, identical HTML output). Under sustained HTTP load on a 24-product store page, assembling each response with a single join lowers the server's resident memory after load from 793 MiB to 527 MiB (see #12006, #12016, #12018, and #12020). (#12074)

  Apps that render client entries also benefit from getScriptEntry() caching in remix/assets: a warm lookup takes about 3 µs instead of 210 µs (see #12005). See the @remix-run/component and @remix-run/assets changelogs for details.

• Use frame.reload({ src, method, encType, body }) from remix/component to reload another source or submit data and render the response without changing browser history. FormData follows GET query and POST encoding defaults, with multipart and plain-text encodings available. (#11938)

• Prefetch frame HTML and assets with data-rmx-prefetch="intent", data-rmx-prefetch="viewport", or the imperative prefetch() API from remix/component. Both link modes support named frames and source overrides, respect Save-Data, and skip slow-2g/2g connections. See the prefetching guide for usage, customization, and caching behavior. (#12004)

• Opt out of automatic focus resets during intercepted navigation with resetFocus: 'manual' in navigate() and link(), or data-rmx-reset-focus="manual" on links, forms, and submit buttons. Scroll and focus controls in remix/component now accept the Navigation API values "after-transition" (the default) and "manual"; existing boolean values remain supported. (#11939)

• remix/file-storage/s3 now streams files to S3 with multipart uploads in storage.set(), so large files no longer need to fit in memory. A new partSize option controls the size of each part. See the @remix-run/file-storage-s3 changelog for details. (#12070)

• Add remix/multipart-parser/future, remix/form-data-parser/future, and remix/middleware/form-data/future, which stream multipart parts and file uploads instead of buffering them in memory. Future APIs are not stable and may change in any release, but they are a good indication of where these packages will land in Remix's next major release. (#12030)

  In our benchmarks, parsing a request with a 100 MiB file upload takes 37 ms instead of 68 ms, the upload handler is called after 0.2 ms instead of 45 ms, and peak memory grows by 29 MiB instead of 396 MiB. Small forms perform the same as before. See the @remix-run/form-data-parser changelog for the full comparison.

  To try it in an app, import formData() from the /future entrypoint. Its options are the same as the stable middleware:

  -import { formData } from 'remix/middleware/form-data'
  +import { formData } from 'remix/middleware/form-data/future'
  
   export const router = createRouter({
     middleware: [
       formData({
         async uploadHandler(upload) {
           let key = crypto.randomUUID()
           await storage.set(key, upload)
           return key
         },
       }),
     ],
   })

  Each upload streams from the request body, so read it inside uploadHandler (for example by passing it to storage.set()). It can be read only once, upload.size is not available until it has been read, and upload.slice() is not supported. Uploads the handler returns unread are read into a regular File. Paired with the new streaming set() in remix/file-storage/s3, large uploads go straight to S3 without being held in memory.

  If your app handles file uploads, please give these entrypoints a try and tell us how it goes in GitHub Discussions. We'd especially like to hear about anything that breaks, behaves unexpectedly, or feels awkward, since that feedback will shape the next major release.

• The remix/* entrypoints now preserve default exports from their underlying packages, including the callable assertion helper from remix/assert and SuperHeaders from remix/headers. (#12061)

  Added package.json exports:

  • remix/form-data-parser/future to re-export APIs from @remix-run/form-data-parser/future
  • remix/middleware/form-data/future to re-export APIs from @remix-run/form-data-middleware/future
  • remix/multipart-parser/future to re-export APIs from @remix-run/multipart-parser/future

• Ensure client entries requested after an HMR update use current cache-busting URLs. (#11980)

• Include unsafeHTML() guidance in remix/component raw HTML prop errors (innerHTML, srcDoc, and srcdoc) and clarify that outerHTML is not supported on host elements. (#11988)

• Bumped @remix-run/* dependencies:

  • assets@1.0.1
  • cli@1.0.1
  • component@1.1.0
  • compression-middleware@1.0.1
  • cookie@1.0.1
  • cors-middleware@1.0.1
  • fetch-proxy@1.0.1
  • file-storage-s3@1.1.0
  • form-data-middleware@1.1.0
  • form-data-parser@1.1.0
  • headers@1.0.1
  • multipart-parser@1.1.0
  • render-middleware@1.0.1
  • response@1.0.1
  • session-middleware@1.0.1
  • spa@1.0.1
  • static-middleware@1.0.1
  • tar-parser@1.0.1

• Bumped @remix-run/* dependencies:
  • response@1.0.1

• Bumped @remix-run/* dependencies:
  • cookie@1.0.1