Version Packages

[workers-devprod]

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

• #7715 26fa9e8 Thanks @penalosa! - Support service bindings from Pages projects to Workers in a single workerd instance. To try it out, pass multiple -c flags to Wrangler: i.e. wrangler pages dev -c wrangler.toml -c ../other-worker/wrangler.toml. The first -c flag must point to your Pages config file, and the rest should point to Workers that are bound to your Pages project.

• #7816 f6cc029 Thanks @dario-piotrowicz! - add support for assets bindings to getPlatformProxy

  this change makes sure that that getPlatformProxy, when the input configuration
  file contains an assets field, correctly returns the appropriate asset binding proxy

  example:

  // wrangler.json
  {
    "name": "my-worker",
    "assets": {
      "directory": "./public/",
      "binding": "ASSETS"
    },
    "vars": {
      "MY_VAR": "my-var"
    }
  }

  import { getPlatformProxy } from "wrangler";
  
  const { env, dispose } = await getPlatformProxy();
  
  if (env.ASSETS) {
    const text = await (
      await env.ASSETS.fetch("http://0.0.0.0/file.txt")
    ).text();
    console.log(text); // logs the content of file.txt
  }
  
  await dispose();

Patch Changes

• #7785 cccfe51 Thanks @joshthoward! - Fix Durable Objects transfer migration validation

• #7821 fcaa02c Thanks @vicb! - fix(wrangler): fix wrangler config schema defaults

• #7832 97d2a1b Thanks @petebacondarwin! - Relax the messaging when Wrangler uses redirected configuration

  Previously the messaging was rendered as a warning, which implied that the user
  had done something wrong. Now it is just a regular info message.

• #7806 d7adb50 Thanks @vicb! - chore: update unenv to 2.0.0-rc.0

  Pull a couple changes in node:timers

  • fix(timers): bind global functions unjs/unenv#384 fix function bindings in node:timer
  • feat(timers): implement active and _unrefActive exports unjs/unenv#385 implement active and _unrefActive in node:timer

  The unenv update also includes #unjs/unenv/381 which implements
  stdout, stderr and stdin of node:process with node:tty

• #7828 9077a67 Thanks @edmundhung! - improve multi account error message in non-interactive mode

• Updated dependencies []:

  • [email protected]

[email protected]

Patch Changes

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

  The following dependency versions have been updated:

  Dependency	From	To
  sv	0.6.11	0.6.13

• #7823 4f84172 Thanks @dependabot! - chore: update dependencies of "create-cloudflare" package

  The following dependency versions have been updated:

  Dependency	From	To
  create-next-app	15.1.4	15.1.5

• #7824 794b446 Thanks @dependabot! - chore: update dependencies of "create-cloudflare" package

  The following dependency versions have been updated:

  Dependency	From	To
  @angular/create	19.0.7	19.1.2

• #7827 6c2e943 Thanks @edmundhung! - fix: bump vitest-pool-workers version range in templates

  This resolves #7815, where users encountered an error about missing nodejs_compat or nodejs_compat_v2 compatibility flags when running Vitest on a fresh Hello World project created with create-cloudflare.

@cloudflare/[email protected]

Patch Changes

• #7806 d7adb50 Thanks @vicb! - chore: update unenv to 2.0.0-rc.0

  Pull a couple changes in node:timers

  • fix(timers): bind global functions unjs/unenv#384 fix function bindings in node:timer
  • feat(timers): implement active and _unrefActive exports unjs/unenv#385 implement active and _unrefActive in node:timer

  The unenv update also includes #unjs/unenv/381 which implements
  stdout, stderr and stdin of node:process with node:tty

@cloudflare/[email protected]

Patch Changes

• #7763 7e04493 Thanks @petebacondarwin! - Initial beta release of the Cloudflare Vite plugin

• Updated dependencies [cccfe51, fcaa02c, 26fa9e8, 97d2a1b, d7adb50, f6cc029, 9077a67]:

  • [email protected]
  • [email protected]

@cloudflare/[email protected]

Patch Changes

• Updated dependencies [cccfe51, fcaa02c, 26fa9e8, 97d2a1b, d7adb50, f6cc029, 9077a67]:
  • [email protected]
  • [email protected]

@cloudflare/[email protected]

Patch Changes

• #7808 7faabeb Thanks @WalshyDev! - fix: fix analytics not being logged for asset-worker in the case of a successful request.

[github-actions]

A wrangler prerelease is available for testing. You can install this latest build in your project with:

npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/12890716848/npm-package-wrangler-7825

You can reference the automatically updated head of this PR with:

npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/prs/7825/npm-package-wrangler-7825

Or you can use npx with this latest build directly:

npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/12890716848/npm-package-wrangler-7825 dev path/to/script.js

Additional artifacts:

cloudflare-workers-bindings-extension:

wget https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/12890716848/npm-package-cloudflare-workers-bindings-extension-7825 -O ./cloudflare-workers-bindings-extension.0.0.0-vc5e4b0ed7.vsix && code --install-extension ./cloudflare-workers-bindings-extension.0.0.0-vc5e4b0ed7.vsix

create-cloudflare:

npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/12890716848/npm-package-create-cloudflare-7825 --no-auto-update

@cloudflare/kv-asset-handler:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/12890716848/npm-package-cloudflare-kv-asset-handler-7825

miniflare:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/12890716848/npm-package-miniflare-7825

@cloudflare/pages-shared:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/12890716848/npm-package-cloudflare-pages-shared-7825

@cloudflare/unenv-preset:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/12890716848/npm-package-cloudflare-unenv-preset-7825

@cloudflare/vite-plugin:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/12890716848/npm-package-cloudflare-vite-plugin-7825

@cloudflare/vitest-pool-workers:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/12890716848/npm-package-cloudflare-vitest-pool-workers-7825

@cloudflare/workers-editor-shared:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/12890716848/npm-package-cloudflare-workers-editor-shared-7825

@cloudflare/workers-shared:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/12890716848/npm-package-cloudflare-workers-shared-7825

@cloudflare/workflows-shared:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/12890716848/npm-package-cloudflare-workflows-shared-7825

Note that these links will no longer work once the GitHub Actions artifact expires.

---

[email protected] includes the following runtime dependencies:

Package	Constraint	Resolved
miniflare	workspace:*	3.20241230.2
workerd	1.20241230.0	1.20241230.0
workerd --version	1.20241230.0	2024-12-30

Please ensure constraints are pinned, and miniflare/workerd minor versions match.

[CarmenPopoviciu]

approved with the following comments for posterity:

• #7806
  I double checked with Victor whether this PR is impacted by cloudflare/workerd#3377. That is not the case since the changes in this PR affect the unenv polyfill only, which does not interract with the native node:timers implemented in workerd

@vicb provided more context here 🙏 ♥️ ....

workerd only implements node:timers in 2025-01-20. That's why unenv
provides a polyfill for the module.

When investigating mysql support, we noted that the package is calling a
deprecated API that was not implemented by unenv. We fixed the issue both in
unenv and in workerd separately. unenv polyfills setImmediate when it is
not available so the workerd problem does not affect unenv.

• #7816
  Anyone have strong opinions against this being a minor?

[farshadjanu1]

.