search

digitalservicebund / achill

Troi client for time-tracking at DigitalService
https://track-your-time.dev.ds4g.net/login
MIT License
1 stars 0 forks source link

Bump @remix-run/react from 2.10.0 to 2.11.0 #68

Closed dependabot[bot] closed 3 months ago

dependabot[bot] commented 3 months ago

Bumps @remix-run/react from 2.10.0 to 2.11.0.

Release notes

Sourced from @​remix-run/react's releases.

v2.11.0

See the changelog for release notes: https://github.com/remix-run/remix/blob/main/CHANGELOG.md#v21110

v2.10.3

See the changelog for release notes: https://github.com/remix-run/remix/blob/main/CHANGELOG.md#v2103

v2.10.2

See the changelog for release notes: https://github.com/remix-run/remix/blob/main/CHANGELOG.md#v2102

v2.10.1

See the changelog for release notes: https://github.com/remix-run/remix/blob/main/CHANGELOG.md#v2101

Changelog

Sourced from @​remix-run/react's changelog.

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

  • Single Fetch: Ensure calls don't include any trailing slash from the pathname (i.e., /path/.data) (#9792)
  • 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

2.10.3

Patch Changes

  • Log any errors encountered loading a route module prior to reloading the page (#8932)
  • Single Fetch (unstable): Proxy request.signal through dataStrategy for loader calls to fix cancellation (#9738)
  • Single Fetch (unstable): Adopt React Router's stabilized future.v7_skipActionErrorRevalidation under the hood (#9706)
    • This also stabilizes the shouldRevalidate parameter from unstable_actionStatus to actionStatus
  • Updated dependencies:
    • @remix-run/server-runtime@2.10.3

2.10.2

Patch Changes

... (truncated)

Commits


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 3 months ago

A newer version of @​remix-run/react exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.

dependabot[bot] commented 3 months ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.