Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Update version for release #10508

Merged
merged 3 commits into from
Feb 27, 2025

Conversation

github-actions[bot]
Copy link
Contributor

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/[email protected]

Minor Changes

  • Add Vite v6 support (#10351)

Patch Changes

@remix-run/[email protected]

Patch Changes

@remix-run/[email protected]

Patch Changes

@remix-run/[email protected]

Patch Changes

@remix-run/[email protected]

Patch Changes

@remix-run/[email protected]

Patch Changes

@remix-run/[email protected]

Patch Changes

@remix-run/[email protected]

Patch Changes

@remix-run/[email protected]

Patch Changes

  • Don't apply Single Fetch revalidation de-optimization when in SPA mode since there is no server HTTP request (#10479)

  • [REMOVE] Bump router (#10505)

  • When using Lazy Route Disscovery (future.v3_lazyRouteDiscovery), Remix will now detect manifest version mismatches after a new deploy and trigger a document reload to sync up any active client sessions with the newly deployed version (#10498)

    • On navigations to undiscovered routes, this mismatch will trigger a document reload of the destination path
    • On fetcher calls to undiscovered routes, this mismatch will trigger a document reload of the current path
    • While performing Eager Route Discovery on rendered <Link> components, mismatches will result in a no-op
  • Updated dependencies:

@remix-run/[email protected]

Patch Changes

@remix-run/[email protected]

Patch Changes

  • When using Lazy Route Disscovery (future.v3_lazyRouteDiscovery), Remix will now detect manifest version mismatches after a new deploy and trigger a document reload to sync up any active client sessions with the newly deployed version (#10498)

    • On navigations to undiscovered routes, this mismatch will trigger a document reload of the destination path
    • On fetcher calls to undiscovered routes, this mismatch will trigger a document reload of the current path
    • While performing Eager Route Discovery on rendered <Link> components, mismatches will result in a no-op

@remix-run/[email protected]

Patch Changes

[email protected]

[email protected]

remix

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

@remix-run/[email protected]

@remix-run/[email protected]

@remix-run/[email protected]

@remix-run/[email protected]

@remix-run/[email protected]

@brophdawg11 brophdawg11 merged commit 2fbec6a into release-next Feb 27, 2025
8 of 9 checks passed
@brophdawg11 brophdawg11 deleted the changeset-release/release-next branch February 27, 2025 17:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant