Skip to content

Conversation

@workers-devprod
Copy link
Contributor

@workers-devprod workers-devprod commented Aug 7, 2025

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 80960b9 Thanks @WillTaylorDev! - Support long branch names in generation of branch aliases in WCI.

  • #10312 bd8223d Thanks @devin-ai-integration! - Added --domain flag to wrangler deploy command for deploying to custom domains. Use --domain example.com to deploy directly to a custom domain without manually configuring routes.

  • #8318 8cf47f9 Thanks @gnekich! - Introduce json output flag for wrangler pages deployment list

Patch Changes

  • #10232 e7cae16 Thanks @emily-shen! - fix: validate wrangler containers delete ID to 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 3b6ab8a Thanks @dom96! - Removes mention of cf-requirements when Python Workers are enabled

  • #10259 c58a05c Thanks @dario-piotrowicz! - Ensure that maybeStartOrUpdateRemoteProxySession considers the potential account_id from the user's wrangler config

    Currently if the user has an account_id in 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 the auth option of maybeStartOrUpdateRemoteProxySession, if provided, takes precedence over this id value).

    The changes here also fix the same issue for wrangler dev and getPlatformProxy (since they use maybeStartOrUpdateRemoteProxySession under the hook).

  • #10288 42aafa3 Thanks @tgarg-cf! - Do not attempt to update queue producer settings when deploying a Worker with a queue binding

    Previously, 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 70bd966 Thanks @devin-ai-integration! - Add experimental API to expose Wrangler command tree structure for documentation generation

  • #10258 d391076 Thanks @nikitassharma! - Add the option to allow all tiers when creating a container

  • #10248 422ae22 Thanks @emily-shen! - fix: re-push container images on deploy even if the only change was to the Dockerfile

  • #10179 5d5ecd5 Thanks @pombosilva! - Prevent defining multiple workflows with the same "name" property in the same wrangler file

  • #10232 e7cae16 Thanks @emily-shen! - include containers API calls in output of WRANGLER_LOG=debug

  • #10243 d481901 Thanks @devin-ai-integration! - Remove async_hooks polyfill - now uses native workerd implementation

    The 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 9aad334 Thanks @edmundhung! - refactor: switch getPlatformProxy() to use Miniflare's dev registry implementation

    Updated 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 28494f4 Thanks @dario-piotrowicz! - fix NonRetryableError thrown with an empty error message not stopping workflow retries locally

  • Updated dependencies [1479fd0, 05c5b28, e3d9703, d481901]:

[email protected]

Patch Changes

  • #9940 46df88c Thanks @stof! - Enable the nodejs_als in the svelte template to work out of the box

  • #10299 eb712ef Thanks @dependabot! - chore: update dependencies of "create-cloudflare" package

    The following dependency versions have been updated:

    Dependency From To
    create-solid 0.6.5 0.6.7
  • #10300 031edad Thanks @dependabot! - chore: update dependencies of "create-cloudflare" package

    The following dependency versions have been updated:

    Dependency From To
    gatsby 5.14.5 5.14.6
  • #10301 c4fa63c Thanks @dependabot! - chore: update dependencies of "create-cloudflare" package

    The following dependency versions have been updated:

    Dependency From To
    create-vite 7.0.3 7.1.0
  • #10302 17e32a5 Thanks @dependabot! - chore: update dependencies of "create-cloudflare" package

    The following dependency versions have been updated:

    Dependency From To
    create-react-router 7.7.1 7.8.0
  • #10303 151b3ce Thanks @dependabot! - chore: update dependencies of "create-cloudflare" package

    The following dependency versions have been updated:

    Dependency From To
    create-next-app 15.3.5 15.4.6
  • #10304 2915f42 Thanks @dependabot! - chore: update dependencies of "create-cloudflare" package

    The following dependency versions have been updated:

    Dependency From To
    @angular/create 20.1.4 20.1.5

[email protected]

Patch Changes

  • #10273 1479fd0 Thanks @edmundhung! - fix: support WebSocket proxying to workerd

    The 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 05c5b28 Thanks @edmundhung! - fix: enable HTTPS support when proxying to workerd

    The Miniflare dev-registry proxy previously assumed workerd would always use HTTP,
    so enabling https on miniflare might caused connection failures in some setups.

    This ensures proxying works whether the option is enabled or not.

  • #10142 e3d9703 Thanks @edmundhung! - fix: support mf.getBindings() when dev registry is enabled

    Fixes 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

@cloudflare/[email protected]

Patch Changes

  • #10243 d481901 Thanks @devin-ai-integration! - Remove async_hooks polyfill - now uses native workerd implementation

    The 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

@cloudflare/[email protected]

Patch Changes

@cloudflare/[email protected]

Minor Changes

@cloudflare/[email protected]

Patch Changes

[email protected]

Patch Changes

@cloudflare/[email protected]

Patch Changes

@workers-devprod workers-devprod requested review from a team as code owners August 7, 2025 10:42
@pkg-pr-new
Copy link

pkg-pr-new bot commented Aug 7, 2025

create-cloudflare

npm i https://pkg.pr.new/create-cloudflare@10263

@cloudflare/kv-asset-handler

npm i https://pkg.pr.new/@cloudflare/kv-asset-handler@10263

miniflare

npm i https://pkg.pr.new/miniflare@10263

@cloudflare/pages-shared

npm i https://pkg.pr.new/@cloudflare/pages-shared@10263

@cloudflare/unenv-preset

npm i https://pkg.pr.new/@cloudflare/unenv-preset@10263

@cloudflare/vite-plugin

npm i https://pkg.pr.new/@cloudflare/vite-plugin@10263

@cloudflare/vitest-pool-workers

npm i https://pkg.pr.new/@cloudflare/vitest-pool-workers@10263

@cloudflare/workers-editor-shared

npm i https://pkg.pr.new/@cloudflare/workers-editor-shared@10263

wrangler

npm i https://pkg.pr.new/wrangler@10263

commit: d287099

@workers-devprod workers-devprod force-pushed the changeset-release/main branch 15 times, most recently from 22774b4 to 978e953 Compare August 10, 2025 21:27
@workers-devprod workers-devprod requested a review from a team August 10, 2025 21:27
@workers-devprod workers-devprod force-pushed the changeset-release/main branch 11 times, most recently from 8283761 to 1ee5fa5 Compare August 11, 2025 11:28
@workers-devprod workers-devprod force-pushed the changeset-release/main branch 7 times, most recently from 004c855 to 265c33b Compare August 12, 2025 10:07
@CarmenPopoviciu CarmenPopoviciu merged commit 1b0b22b into main Aug 12, 2025
52 of 58 checks passed
@CarmenPopoviciu CarmenPopoviciu deleted the changeset-release/main branch August 12, 2025 17:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants