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.

Sign up for GitHub

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

Jump to bottom

chore: Update version for release (pre) #9150

Merged
merged 2 commits into from
Mar 27, 2024
Merged

chore: Update version for release (pre) #9150

merged 2 commits into from
Mar 27, 2024

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.

⚠️⚠️⚠️⚠️⚠️⚠️

release-next is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on release-next.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

@remix-run/[email protected]

Minor Changes

  • New future.unstable_singleFetch flag (#8773)

    • Naked objects returned from loaders/actions are no longer automatically converted to JSON responses. They'll be streamed as-is via turbo-stream so Date's will become Date through useLoaderData()
    • You can return naked objects with Promise's without needing to use defer() - including nested Promise's
      • If you need to return a custom status code or custom response headers, you can still use the defer utility
    • <RemixServer abortDelay> is no longer used. Instead, you should export const streamTimeout from entry.server.tsx and the remix server runtime will use that as the delay to abort the streamed response
      • If you export your own streamTimeout, you should decouple that from aborting the react renderToPipeableStream. You should always ensure that react is aborted afer the stream is aborted so that abort rejections can be flushed down
    • Actions no longer automatically revalidate on 4xx/5xx responses (via RR future.unstable_skipActionErrorRevalidation flag) - you can return a 2xx to opt-into revalidation or use shouldRevalidate

Patch Changes

@remix-run/[email protected]

Minor Changes

Patch Changes

@remix-run/[email protected]

Minor Changes

  • New future.unstable_singleFetch flag (#8773)

    • Naked objects returned from loaders/actions are no longer automatically converted to JSON responses. They'll be streamed as-is via turbo-stream so Date's will become Date through useLoaderData()
    • You can return naked objects with Promise's without needing to use defer() - including nested Promise's
      • If you need to return a custom status code or custom response headers, you can still use the defer utility
    • <RemixServer abortDelay> is no longer used. Instead, you should export const streamTimeout from entry.server.tsx and the remix server runtime will use that as the delay to abort the streamed response
      • If you export your own streamTimeout, you should decouple that from aborting the react renderToPipeableStream. You should always ensure that react is aborted afer the stream is aborted so that abort rejections can be flushed down
    • Actions no longer automatically revalidate on 4xx/5xx responses (via RR future.unstable_skipActionErrorRevalidation flag) - you can return a 2xx to opt-into revalidation or use shouldRevalidate

Patch Changes

  • fix: escape single fetch transfer (#9084)
  • Update single fetch implementation to avoid over-fetching when clientLoader's exist (#9073)
  • Updated dependencies:

@remix-run/[email protected]

Minor Changes

  • New future.unstable_singleFetch flag (#8773)

    • Naked objects returned from loaders/actions are no longer automatically converted to JSON responses. They'll be streamed as-is via turbo-stream so Date's will become Date through useLoaderData()
    • You can return naked objects with Promise's without needing to use defer() - including nested Promise's
      • If you need to return a custom status code or custom response headers, you can still use the defer utility
    • <RemixServer abortDelay> is no longer used. Instead, you should export const streamTimeout from entry.server.tsx and the remix server runtime will use that as the delay to abort the streamed response
      • If you export your own streamTimeout, you should decouple that from aborting the react renderToPipeableStream. You should always ensure that react is aborted afer the stream is aborted so that abort rejections can be flushed down
    • Actions no longer automatically revalidate on 4xx/5xx responses (via RR future.unstable_skipActionErrorRevalidation flag) - you can return a 2xx to opt-into revalidation or use shouldRevalidate

Patch Changes

  • handle net new redirects created by handleDataRequest (#9104)

  • Add ResponseStub header interface for single fetch and deprecate the headers export (#9142)

    • The headers export is no longer used when single fetch is enabled
    • loader/action functions now receive a mutable response parameter
      • type ResponseStub = { status: numbers | undefined, headers: Headers }
    • To alter the status of a response, set the status field directly
      • response.status = 201
    • To set headers on the Response, you may use:
      • response.headers.set
      • response.headers.append
      • response.headers.delete
    • Each loader/actionreceives it's own unique response instance so you cannot see what other loader/action functions have set (which would be subject to race conditions)
    • If all status codes are unset or have values <200, the deepest status code will be used for the HTTP response
    • If any status codes are set to a value >=300, the highest >=300 value will be used for the HTTP Response
    • Remix tracks header operations and will replay them in order (action if present, then loaders top-down) after all handlers have completed on a fresh Headers instance that will be applied to the HTTP Response
      • headers.set on any child handler will overwrite values from parent handlers
      • headers.append can be used to set the same header from both a parent and child handler
      • headers.delete can be used to delete a value set by a parent handler, but not a value set from a child handler
    • Because single fetch supports naked object returns, and you no longer need to return a Response instance to set status/headers, the json/redirect/redirectDocument/defer utilities are considered deprecated when using Single Fetch
    • You may still continue returning normal Response instances and they'll apply status codes in the same way, and will apply all headers via headers.set - overwriting any same-named header values from parents
      • If you need to append, you will need to switch from returning a Response instance to using the new response parameter

@remix-run/[email protected]

Minor Changes

  • New future.unstable_singleFetch flag (#8773)

    • Naked objects returned from loaders/actions are no longer automatically converted to JSON responses. They'll be streamed as-is via turbo-stream so Date's will become Date through useLoaderData()
    • You can return naked objects with Promise's without needing to use defer() - including nested Promise's
      • If you need to return a custom status code or custom response headers, you can still use the defer utility
    • <RemixServer abortDelay> is no longer used. Instead, you should export const streamTimeout from entry.server.tsx and the remix server runtime will use that as the delay to abort the streamed response
      • If you export your own streamTimeout, you should decouple that from aborting the react renderToPipeableStream. You should always ensure that react is aborted afer the stream is aborted so that abort rejections can be flushed down
    • Actions no longer automatically revalidate on 4xx/5xx responses (via RR future.unstable_skipActionErrorRevalidation flag) - you can return a 2xx to opt-into revalidation or use shouldRevalidate

Patch Changes

[email protected]

Patch Changes

  • Allow . in repo name when using --template flag (#9026)

@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

[email protected]

remix

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

@remix-run/[email protected]

@remix-run/[email protected]

@brophdawg11 brophdawg11 merged commit e3e4403 into release-next Mar 27, 2024
9 checks passed
@brophdawg11 brophdawg11 deleted the changeset-release/release-next branch March 27, 2024 17:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
CLA Signed
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@brophdawg11