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
#10283
80960b9Thanks @WillTaylorDev! - Support long branch names in generation of branch aliases in WCI.#10312
bd8223dThanks @devin-ai-integration! - Added--domainflag towrangler deploycommand for deploying to custom domains. Use--domain example.comto deploy directly to a custom domain without manually configuring routes.#8318
8cf47f9Thanks @gnekich! - Introduce json output flag for wrangler pages deployment listPatch Changes
#10232
e7cae16Thanks @emily-shen! - fix: validatewrangler containers delete IDto ensure a valid ID has been provided. Previously if you provided the container name (or any non-ID shaped string) you would get an auth error instead of a 404.#10139
3b6ab8aThanks @dom96! - Removes mention of cf-requirements when Python Workers are enabled#10259
c58a05cThanks @dario-piotrowicz! - Ensure thatmaybeStartOrUpdateRemoteProxySessionconsiders the potential account_id from the user's wrangler configCurrently if the user has an
account_idin their wrangler config file, such id won't be taken into consideration for the remote proxy session, the changes here make sure that it is (note that theauthoption ofmaybeStartOrUpdateRemoteProxySession, if provided, takes precedence over this id value).The changes here also fix the same issue for
wrangler devandgetPlatformProxy(since they usemaybeStartOrUpdateRemoteProxySessionunder the hook).#10288
42aafa3Thanks @tgarg-cf! - Do not attempt to update queue producer settings when deploying a Worker with a queue bindingPreviously, each deployed Worker would update a subset of the queue producer's settings for each queue binding, which could result in broken queue producers or at least conflicts where different Workers tried to set different producer settings on a shared queue.
#10242
70bd966Thanks @devin-ai-integration! - Add experimental API to expose Wrangler command tree structure for documentation generation#10258
d391076Thanks @nikitassharma! - Add the option to allow all tiers when creating a container#10248
422ae22Thanks @emily-shen! - fix: re-push container images on deploy even if the only change was to the Dockerfile#10179
5d5ecd5Thanks @pombosilva! - Prevent defining multiple workflows with the same "name" property in the same wrangler file#10232
e7cae16Thanks @emily-shen! - include containers API calls in output of WRANGLER_LOG=debug#10243
d481901Thanks @devin-ai-integration! - Remove async_hooks polyfill - now uses native workerd implementationThe async_hooks module is now provided natively by workerd, making the polyfill unnecessary. This improves performance and ensures better compatibility with Node.js async_hooks APIs.
#10060
9aad334Thanks @edmundhung! - refactor: switchgetPlatformProxy()to use Miniflare's dev registry implementationUpdated
getPlatformProxy()to use Miniflare's dev registry instead of Wrangler's implementation. Previously, you had to start a wrangler or vite dev session before accessing the proxy bindings to connect to those workers. Now the order doesn't matter.#10219
28494f4Thanks @dario-piotrowicz! - fixNonRetryableErrorthrown with an empty error message not stopping workflow retries locallyUpdated dependencies [
1479fd0,05c5b28,e3d9703,d481901]:[email protected]
Patch Changes
#9940
46df88cThanks @stof! - Enable the nodejs_als in the svelte template to work out of the box#10299
eb712efThanks @dependabot! - chore: update dependencies of "create-cloudflare" packageThe following dependency versions have been updated:
#10300
031edadThanks @dependabot! - chore: update dependencies of "create-cloudflare" packageThe following dependency versions have been updated:
#10301
c4fa63cThanks @dependabot! - chore: update dependencies of "create-cloudflare" packageThe following dependency versions have been updated:
#10302
17e32a5Thanks @dependabot! - chore: update dependencies of "create-cloudflare" packageThe following dependency versions have been updated:
#10303
151b3ceThanks @dependabot! - chore: update dependencies of "create-cloudflare" packageThe following dependency versions have been updated:
#10304
2915f42Thanks @dependabot! - chore: update dependencies of "create-cloudflare" packageThe following dependency versions have been updated:
[email protected]
Patch Changes
#10273
1479fd0Thanks @edmundhung! - fix: support WebSocket proxying to workerdThe dev registry proxy server now correctly handles WebSocket upgrade requests and
tunnels bidirectional frames between the workerd processes. Previously,
handshakes would fail due to missing upgrade logic.
#10281
05c5b28Thanks @edmundhung! - fix: enable HTTPS support when proxying to workerdThe Miniflare dev-registry proxy previously assumed workerd would always use HTTP,
so enabling
httpson miniflare might caused connection failures in some setups.This ensures proxying works whether the option is enabled or not.
#10142
e3d9703Thanks @edmundhung! - fix: supportmf.getBindings()when dev registry is enabledFixes a deadlock when using bindings from
mf.getBindings()with the dev registry enabled. The deadlock happened because the runtime attempted to resolve a worker address via the loopback server, which was blocked by the Node.js thread waiting on the same runtime.Address lookup has been moved to a proxy running in a worker thread to avoid blocking the main thread.
@cloudflare/[email protected]
Patch Changes
1479fd0,05c5b28,e3d9703]:@cloudflare/[email protected]
Patch Changes
#10243
d481901Thanks @devin-ai-integration! - Remove async_hooks polyfill - now uses native workerd implementationThe async_hooks module is now provided natively by workerd, making the polyfill unnecessary. This improves performance and ensures better compatibility with Node.js async_hooks APIs.
@cloudflare/[email protected]
Patch Changes
e7cae16,3b6ab8a,c58a05c,42aafa3,70bd966,d391076,422ae22,1479fd0,80960b9,05c5b28,5d5ecd5,e3d9703,bd8223d,e7cae16,d481901,9aad334,28494f4,8cf47f9]:@cloudflare/[email protected]
Patch Changes
e7cae16,3b6ab8a,c58a05c,42aafa3,70bd966,d391076,422ae22,1479fd0,80960b9,05c5b28,5d5ecd5,e3d9703,bd8223d,e7cae16,d481901,9aad334,28494f4,8cf47f9]:@cloudflare/[email protected]
Minor Changes
a4c4c5bThanks @penalosa! - Bump base VSCode version for Quick Edit & Playground to 1.102.1@cloudflare/[email protected]
Patch Changes
#10258
d391076Thanks @nikitassharma! - Add the option to allow all tiers when creating a container#10232
e7cae16Thanks @emily-shen! - include containers API calls in output of WRANGLER_LOG=debug[email protected]
Patch Changes
#10270
7caf49eThanks @petebacondarwin! - fix security alerts to avoid being in the same notification thread#10269
469f6eeThanks @devin-ai-integration! - Remove PR summary messages and PR update notifications from devprod-status-bot Worker@cloudflare/[email protected]
Patch Changes
28494f4Thanks @dario-piotrowicz! - fixNonRetryableErrorthrown with an empty error message not stopping workflow retries locally