what stackpulse tracks
Remix releases from GitHub
StackPulse watches Remix release notes and keeps the original source link close to every summary.
#stacks/
loading releases…
releases
breaking
security
deprecated
migrations
Full stack web framework with focus on web standards StackPulse turns upstream changelogs into scannable summaries with risky changes, deprecations, migration notes, and source links.
what stackpulse tracks
StackPulse watches Remix release notes and keeps the original source link close to every summary.
upgrade risk
Risky changes are separated from normal feature notes so you can scan upgrade impact before changing production dependencies.
migration notes
Migration steps and recommended actions are only shown when the upstream release notes support them.
This release introduces stricter default path validation and new size limits for tar archive parsing. Applications must explicitly opt into unrestricted path handling or larger archive processing.
Applications processing tar archives with unrestricted paths or large archives will need to update their configuration.
Review and update tar archive parsing configurations to handle path validation and size limits as needed.
This patch release updates internal `@remix-run/*` dependencies to their latest versions.
view source on github->This release primarily updates internal dependencies to their latest versions, including `fetch-router`, `render-middleware`, and `ui`.
Users relying on `@remix-run/*` dependencies may need to ensure compatibility with the updated versions.
Review dependency updates and test for compatibility.
This release introduces several breaking changes related to frame navigation, HTML prop handling, and security improvements. It also includes patches to fix hydration issues, event handler duplication, and frame restoration.
Developers using named frame navigation, cross-origin frame content, or raw HTML props are affected.
Review and update code to comply with the new navigation, `resolveFrame`, and HTML prop handling requirements.
This patch fixes an issue where server-only test runs would fail if Playwright was not installed as a peer dependency.
Users running server-only tests with Remix are affected by the Playwright dependency issue.
Update to v0.6.1 if you're running server-only tests without Playwright installed.
This release bumps the @remix-run dependencies to version 0.22.0, specifically fetch-router.
Users of static-middleware who also use @remix-run dependencies may need to update their dependencies.
Update @remix-run dependencies to version 0.22.0 if used alongside static-middleware.
This patch release updates several `@remix-run/*` dependencies to their latest versions, including `fetch-router@0.22.0`, `render-middleware@0.3.0`, and `ui@0.9.0`.
Users relying on specific `@remix-run/*` dependencies may need to ensure compatibility with the updated versions.
Update `@remix-run/*` dependencies to the specified versions if needed.
This patch release updates the `@remix-run/*` dependencies to version 0.22.0 for fetch-router.
Users of session-middleware who also use `@remix-run/*` dependencies may need to update their dependencies.
Update `@remix-run/*` dependencies to their latest versions if using session-middleware.
This release introduces support for import maps in client entries and enhances frame navigation with improved scroll behavior and error handling. It also adds new capabilities for handling client entry preloads and fixes several bugs related to frame rendering and navigation.
Developers using client entries and frame navigation in Remix will benefit from the new features and bug fixes.
This release introduces a breaking change in the `render` method, requiring custom asset server implementations to provide `getScriptEntry()` instead of `getHref()` and `getPreloads()`. It also includes dependency updates for `@remix-run/*` packages.
Developers using custom asset server implementations are affected by this change.
Update custom asset server implementations to provide `getScriptEntry()` instead of `getHref()` and `getPreloads()`.
This release introduces the initial `@remix-run/spa` package, providing middleware and browser runtime for client-rendered Remix applications. It maintains the router's request/response contract while adding SPA-specific functionality.
Developers using Remix for client-rendered applications are affected by this new SPA package.
Consider using the new `@remix-run/spa` package for client-rendered Remix applications.
This release introduces a new `render` function for request-scoped Remix UI rendering, enabling typed HTML responses, nested frame resolution, and optional asset server integration.
Developers using Remix for UI rendering will benefit from the new `render` function and its enhanced capabilities.
Update to `render-middleware@0.2.0` to leverage the new `render` function and its features.
This release introduces breaking changes to DOM attribute namespaces and server rendering behavior, while adding a new SPA response protocol. It also includes several fixes for rendering, navigation, and scroll behavior.
Developers using Remix UI framework-owned DOM attributes, server-rendered script elements with non-string children, or the `addEventListeners()` helper are affected.
Update all Remix UI framework-owned DOM attributes to use the new `data-rmx-*` namespace and replace `addEventListeners()` with native event listeners.
This release bumps the `@remix-run/*` dependencies to version 0.5.0 of the data-table package.
Users of data-table-sqlite who also use @remix-run dependencies may need to update their dependencies.
Update @remix-run dependencies to compatible versions.
This release introduces a rollback command for database migrations and improves filter composition with object shorthand support.
Users of `runRemixDb()` or the `remix db` CLI are affected by the new rollback functionality.
Update to utilize the new rollback functionality and object shorthand filters if needed.
This patch release updates `@remix-run/fetch-router` to ^0.21.0 to fix type incompatibilities with other router middleware, maintaining compatibility with Remix 3 projects.
Users of `staticFiles()` middleware in Remix 3 projects may need to update to maintain compatibility.
Update to static-middleware@0.4.14 if using `staticFiles()` middleware in a Remix 3 project.
This release marks the initial release of the static file-serving middleware but is immediately superseded. Users should not use this package and instead use the recommended alternatives.
Users of the `static-files-middleware` package are affected as it is now superseded.
Migrate to `@remix-run/static-middleware` or use `staticFiles` from `remix/middleware/static`.
This release updates the default app template for `remix new` to include preloads for client entries, improving performance.
Users creating new Remix apps will benefit from improved client entry preloading.
This beta release includes fixes for type checking issues with middleware and simplifies frame handling in `remix/ui`. However, it is superseded by beta.10 and should not be used.
Developers using `staticFiles()` and other router middleware together in fresh Remix projects are affected by type checking failures.
Upgrade to `remix@3.0.0-beta.10` or newer as this beta version is superseded.
This release introduces a default browser frame resolver in `run()`, simplifying configuration for basic use cases while maintaining support for custom resolvers when needed. It also enhances navigation capabilities through the Navigation API.
Developers using custom `resolveFrame` implementations for basic HTML fetching in `run()` are affected.
Review and potentially remove custom `resolveFrame` implementations if they match the default behavior.