chore: Update version for release (pre) #9199
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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, runchangeset pre exit
onrelease-next
.Releases
@remix-run/architect@2.9.0-pre.3
Patch Changes
@remix-run/node@2.9.0-pre.3
@remix-run/cloudflare@2.9.0-pre.3
Patch Changes
@remix-run/server-runtime@2.9.0-pre.3
@remix-run/cloudflare-pages@2.9.0-pre.3
Patch Changes
@remix-run/cloudflare@2.9.0-pre.3
@remix-run/cloudflare-workers@2.9.0-pre.3
Patch Changes
@remix-run/cloudflare@2.9.0-pre.3
@remix-run/deno@2.9.0-pre.3
Patch Changes
@remix-run/server-runtime@2.9.0-pre.3
@remix-run/dev@2.9.0-pre.3
Patch Changes
@remix-run/node@2.9.0-pre.3
@remix-run/server-runtime@2.9.0-pre.3
@remix-run/express@2.9.0-pre.3
Patch Changes
@remix-run/node@2.9.0-pre.3
@remix-run/node@2.9.0-pre.3
Patch Changes
undici
fetch polyfill behind a newinstallGlobals({ nativeFetch: true })
parameter (#9198)remix-serve
will default to usingundici
for the fetch polyfill iffuture._unstable_singleFetch
is enabled because the single fetch implementation relies on theundici
polyfillinstallGlobals
on their own to avoid runtime errors with Single Fetch@remix-run/server-runtime@2.9.0-pre.3
@remix-run/react@2.9.0-pre.3
Patch Changes
@remix-run/server-runtime@2.9.0-pre.3
@remix-run/serve@2.9.0-pre.3
Patch Changes
undici
fetch polyfill behind a newinstallGlobals({ nativeFetch: true })
parameter (#9198)remix-serve
will default to usingundici
for the fetch polyfill iffuture._unstable_singleFetch
is enabled because the single fetch implementation relies on theundici
polyfillinstallGlobals
on their own to avoid runtime errors with Single Fetch@remix-run/node@2.9.0-pre.3
@remix-run/express@2.9.0-pre.3
@remix-run/testing@2.9.0-pre.3
Patch Changes
@remix-run/node@2.9.0-pre.3
@remix-run/react@2.9.0-pre.3
create-remix@2.9.0-pre.3
remix@2.9.0-pre.3
remix
See the
CHANGELOG.md
in individual Remix packages for all changes.@remix-run/css-bundle@2.9.0-pre.3
@remix-run/eslint-config@2.9.0-pre.3
@remix-run/server-runtime@2.9.0-pre.3