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 main, this PR will be updated.
Releases
[email protected]
Minor Changes
af18b48Thanks @dario-piotrowicz! - add TanStack Start framework templatePatch Changes
#10991
0372e86Thanks @dom96! - Adds submodule to Python hello world template#11043
5d9cf0dThanks @dom96! - Remove lockfiles from Python C3 templates@cloudflare/[email protected]
Minor Changes
0ff1964Thanks @petebacondarwin! - Infer latest locally available compatibility date if none is provided in the test configurationPatch Changes
#10919
ca6c010Thanks @Caio-Nogueira! - migrate workflow to use a wrapped binding#11047
0ff1964Thanks @petebacondarwin! - ensure that vitest specific nodejs polyfills override native modules#10741
2f57345Thanks @penalosa! - Remove obsolete--x-remote-bindingsflagUpdated dependencies [
4bd4c29,31e1330,1a8088a,ca6c010,2f57345]:[email protected]
Minor Changes
#11030
1a8088aThanks @penalosa! - Enable automatic resource provisioning by default in Wrangler. This is still an experimental feature, but we're turning on the flag by default to make it easier for people to test it and try it out. You can disable the feature using the--no-x-provisionflag. It currently works for R2, D1, and KV bindings.To use this feature, add a binding to your config file without a resource ID:
{ "kv_namespaces": [{ "binding": "MY_KV" }], "d1_databases": [{ "binding": "MY_DB" }], "r2_buckets": [{ "binding": "MY_R2" }], }wrangler devwill automatically create these resources for you locally, and when you next runwrangler deployWrangler will call the Cloudflare API to create the requested resources and link them to your Worker. They'll stay linked across deploys, and you don't need to add the resource IDs to the config file for future deploys to work. This is especially good for shared templates, which now no longer need to include account-specific resource ID when adding a binding.Patch Changes
#11037
4bd4c29Thanks @danielrs! - Better Wrangler subdomain defaults warning.Improves the warnings that we show users when either
worker_devorpreview_urlsare missing.#10927
31e1330Thanks @dom96! - Implementspython_modules.excludeswrangler config field#10741
2f57345Thanks @penalosa! - Remove obsolete--x-remote-bindingsflagUpdated dependencies [
ca6c010]:[email protected]
Patch Changes
ca6c010Thanks @Caio-Nogueira! - migrate workflow to use a wrapped binding@cloudflare/[email protected]
Patch Changes
ca6c010]:@cloudflare/[email protected]
Patch Changes
#10741
2f57345Thanks @penalosa! - Remove obsolete--x-remote-bindingsflagUpdated dependencies [
4bd4c29,31e1330,1a8088a,ca6c010,2f57345]:@cloudflare/[email protected]
Patch Changes
ca6c010Thanks @Caio-Nogueira! - migrate workflow to use a wrapped binding