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 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 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 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 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 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.