Minor Changes

• #11728 7d63fa5 Thanks @NuroDev! - Add command categories to wrangler help menu

  The help output now groups commands by product category (Account, Compute & AI, Storage & Databases, Networking & Security) to match the Cloudflare dashboard organization:

  $ wrangler --help
  
  COMMANDS
    wrangler docs [search..]  📚 Open Wrangler's command documentation in your browser
  
  ACCOUNT
    wrangler auth    🔓 Manage authentication
    wrangler login   🔑 Login to Cloudflare
    ...
  
  COMPUTE & AI
    wrangler ai          🤖 Manage AI models
    wrangler containers  📦 Manage Containers [open beta]
    ...
  

  This improves discoverability by organizing the 20+ wrangler commands into logical groups.

Patch Changes

• #11822 97e67b9 Thanks @dependabot! - chore: update dependencies of "miniflare", "wrangler"

  The following dependency versions have been updated:

  Dependency	From	To
  workerd	1.20260103.0	1.20260107.1

• Updated dependencies [97e67b9]:

  • [email protected]

Patch Changes

• #11822 97e67b9 Thanks @dependabot! - chore: update dependencies of "miniflare", "wrangler"

  The following dependency versions have been updated:

  Dependency	From	To
  workerd	1.20260103.0	1.20260107.1

Patch Changes

• #11540 3f2d2c9 Thanks @dependabot! - chore: update dependencies of "create-cloudflare"

  The following dependency versions have been updated:

  Dependency	From	To
  create-hono	0.19.3	0.19.4

• #11542 01b8c2b Thanks @dependabot! - chore: update dependencies of "create-cloudflare"

  The following dependency versions have been updated:

  Dependency	From	To
  sv	0.10.5	0.11.2

• #11546 d7112b6 Thanks @dependabot! - chore: update dependencies of "create-cloudflare"

  The following dependency versions have been updated:

  Dependency	From	To
  @angular/create	21.0.1	21.0.4

• #11638 7ce9240 Thanks @dependabot! - chore: update dependencies of "create-cloudflare"

  The following dependency versions have been updated:

  Dependency	From	To
  create-react-router	7.9.6	7.11.0

• #11762 835bf59 Thanks @dependabot! - chore: update dependencies of "create-cloudflare"

  The following dependency versions have been updated:

  Dependency	From	To
  create-qwik	1.17.2	1.18.0

• #11778 c3b8268 Thanks @rmarscher! - Update Waku framework template wrangler.jsonc main entry path

  Waku changed the worker main entry build path for v1.0. wakujs/waku#1758

  Removed not_found_handling so the worker will be invoked when no asset is found. This avoids 404 errors Waku server-side routes when assets_navigation_prefers_asset_serving is enabled. https://developers.cloudflare.com/workers/configuration/compatibility-flags/#navigation-requests-prefer-asset-serving

Patch Changes

• Updated dependencies [97e67b9, 7d63fa5]:
  • [email protected]
  • [email protected]

Patch Changes

• #11807 fada563 Thanks @jamesopstad! - Use rolldownOptions in plugin config when available.

  This improves compatibility with Vite 8 beta and removes warnings related to use of esbuildOptions.

• Updated dependencies [97e67b9, 7d63fa5]:

  • [email protected]
  • [email protected]

Patch Changes

• Updated dependencies [97e67b9]:
  • [email protected]

Minor Changes

• #11682 b993d95 Thanks @ascorbic! - Add wrangler auth token command to retrieve your current authentication credentials.

  You can now retrieve your authentication token for use with other tools and scripts:

  wrangler auth token

  The command returns whichever authentication method is currently configured:

  • OAuth token from wrangler login (automatically refreshed if expired)
  • API token from CLOUDFLARE_API_TOKEN environment variable

  Use --json to get structured output including the token type, which also supports API key/email authentication:

  wrangler auth token --json

  This is similar to gh auth token in the GitHub CLI.

• #11702 f612b46 Thanks @gpanders! - Add support for trusted_user_ca_keys in Wrangler

  You can now configure SSH trusted user CA keys for containers. Add the following to your wrangler.toml:

  [[containers.trusted_user_ca_keys]]
  public_key = "ssh-ed25519 AAAAC3..."

  This allows you to specify CA public keys that can be used to verify SSH user certificates.

• #11437 9e360f6 Thanks @ichernetsky-cf! - Drop deprecated containers observability.logging field

• #11616 fc95831 Thanks @NuroDev! - Add type generation support to wrangler dev

  You can now have your worker configuration types be automatically generated when the local Wrangler development server starts.

  To use it you can either:

  1. Add the --types flag when running wrangler dev.
  2. Update your Wrangler configuration file to add the new dev.generate_types boolean property.

  {
  	"$schema": "node_modules/wrangler/config-schema.json",
  	"name": "example",
  	"main": "src/index.ts",
  	"compatibility_date": "2025-12-12",
  	"dev": {
  		"generate_types": true
  	}
  }

• #11524 b0dbf1a Thanks @penalosa! - Add hidden CLI flags to wrangler setup for suppressing output

  Two new hidden flags have been added to wrangler setup:

  • --no-completion-message: Suppresses the deployment details message after setup completes
  • --no-install-wrangler: Skips Wrangler installation during project setup

• #11777 69979a3 Thanks @MattieTK! - Add analytics properties to secret commands for better usage insights

  Secret commands (wrangler secret put, wrangler secret bulk, and their Pages/versions equivalents) now include additional analytics properties to help understand how secrets are being managed:

  • secretOperation: Whether this is a "single" or "bulk" secret operation
  • secretSource: How the secret was provided ("interactive", "stdin", or "file")
  • secretFormat: For bulk operations, the format used ("json" or "dotenv")
  • hasEnvironment: Whether an environment was specified

  These properties help improve the developer experience by understanding common usage patterns. No sensitive information (secret names, values, or counts) is tracked.

• #11738 c54f8da Thanks @jamesopstad! - Add default Text module rule for .sql files.

  This enables importing .sql files directly in Wrangler and the Cloudflare Vite plugin without extra configuration.

• #11692 df1f9c9 Thanks @dario-piotrowicz! - Support Waku in autoconfig

• #11549 d059f69 Thanks @dario-piotrowicz! - Support Vike in autoconfig

Patch Changes

• #11683 02fbd22 Thanks @ascorbic! - Display a warning when authentication errors occur and the account_id in your Wrangler configuration does not match any of your authenticated accounts. This helps identify configuration issues where you may have the wrong account ID set in your wrangler.toml or wrangler.jsonc file.

• #11704 77078ef Thanks @dario-piotrowicz! - Fix autoconfig handling of Next.js apps with CJS config files and incompatible Next.js versions

  Previously, wrangler setup and wrangler deploy --x-autoconfig would fail when working with Next.js applications that use CommonJS config files (next.config.cjs) or have versions of Next.js that don't match the required peer dependencies. The autoconfig process now uses dynamic imports and forced installation to handle these scenarios gracefully.

• #11796 2510723 Thanks @dario-piotrowicz! - wrangler deploy delegates to opennextjs-cloudflare deploy only when the --x-autoconfig flag is used

  The wrangler deploy command has been updated to delegate to the opennextjs-cloudflare deploy command when run in an open-next project. Once this behavior had been introduced it caused a few issues. So it's been decided to enable it for the time being only when the --x-autoconfig flag is set (since this behavior, although generally valid, is only strictly necessary for the wrangler deploy's autoconfig flow).

• #11764 9f6dd71 Thanks @terakoya76! - Fix R2 Data Catalog snapshot-expiration API field names

  The wrangler r2 bucket catalog snapshot-expiration enable command was sending incorrect field names
  to the Cloudflare API, resulting in a 422 Unprocessable Entity error. This fix updates the API request
  body to use the correct field names:

  • olderThanDays -> max_snapshot_age (as duration string, e.g., "30d")
  • retainLast -> min_snapshots_to_keep

  The CLI options (--older-than-days and --retain-last) remain unchanged.

• #11651 d123ad0 Thanks @dario-piotrowicz! - Surface a more helpful error message for TOML Date, Date-Time, and Time values in vars

  TOML parses unquoted date/time values like DATE = 2024-01-01 as objects. Previously this would cause an unhelpful error message further down the stack. Now wrangler surfaces a more helpful error message earlier, telling you to quote the value as a string, e.g. DATE = "2024-01-01".

• #11711 5121b23 Thanks @southpolesteve! - Show an error when D1 migration commands are run without a configuration file

  Previously, running wrangler d1 migrations apply, wrangler d1 migrations list, or wrangler d1 migrations create in a directory without a Wrangler configuration file would silently exit with no feedback. Now these commands display a clear error message:

  "No configuration file found. Create a wrangler.jsonc file to define your D1 database."

• #11710 82e7e90 Thanks @dario-piotrowicz! - Fix arguments passed to wrangler deploy not being forwarded to opennextjs-cloudflare deploy

  wrangler deploy run in an open-next project delegates to opennextjs-cloudflare deploy, as part of this all the arguments passed to wrangler deploy need be forwarded to opennextjs-cloudflare deploy, before the arguments would be lost, now they will be successfully forwarded (for example wrangler deploy --keep-vars will call opennextjs-cloudflare deploy --keep-vars)

• #10750 4688f59 Thanks [@jacoblearned](htt...

Minor Changes

• #11648 eac5cf7 Thanks @pombosilva! - Add Workflows test handlers in vitest-pool-workers to get the Workflow instance output and error:

  • getOutput(): Returns the output of the successfully completed Workflow instance.
  • getError(): Returns the error information of the errored Workflow instance.

  Example:

  // First wait for the workflow instance to complete:
  await expect(
  	instance.waitForStatus({ status: "complete" })
  ).resolves.not.toThrow();
  
  // Then, get its output
  const output = await instance.getOutput();
  
  // Or for errored workflow instances, get their error:
  await expect(
  	instance.waitForStatus({ status: "errored" })
  ).resolves.not.toThrow();
  const error = await instance.getError();

Patch Changes

• #11714 65d1850 Thanks @dependabot! - chore: update dependencies of "miniflare" package

  The following dependency versions have been updated:

  Dependency	From	To
  workerd	1.20251217.0	1.20251219.0

• #11732 1615fce Thanks @dependabot! - chore: update dependencies of "miniflare" package

  The following dependency versions have been updated:

  Dependency	From	To
  workerd	1.20251219.0	1.20251221.0

• #11748 b2769bf Thanks @dependabot! - chore: update dependencies of "miniflare" package

  The following dependency versions have been updated:

  Dependency	From	To
  workerd	1.20251221.0	1.20251223.0

• #11791 554a4df Thanks @dependabot! - chore: update dependencies of "miniflare" package

  The following dependency versions have been updated:

  Dependency	From	To
  workerd	1.20251223.0	1.20260103.0

• #11642 8eede3f Thanks @petebacondarwin! - Fix intermittent "Fetch failed" errors in Miniflare tests on Windows

  Miniflare tests would occasionally fail with "Fetch failed" errors (particularly on Windows CI runners) due to race conditions between undici's Keep-Alive mechanism and the Miniflare server closing idle connections. Miniflare now configures the Dispatcher to prevent connection reuse and eliminate these race condition errors.

• #11493 6a05b1c Thanks @GameRoMan! - Update zod from 3.22.3 to 3.25.76

Minor Changes

• #11549 d059f69 Thanks @dario-piotrowicz! - Support Vike in --experimental mode

• #11692 df1f9c9 Thanks @dario-piotrowicz! - Support Waku in --experimental mode

Patch Changes

• #11812 faf8d27 Thanks @dario-piotrowicz! - Remove redundant output present for the experimental setup of frameworks (by using new CLI flags of wrangler setup).

Minor Changes

• #11648 eac5cf7 Thanks @pombosilva! - Add Workflows test handlers in vitest-pool-workers to get the Workflow instance output and error:

  • getOutput(): Returns the output of the successfully completed Workflow instance.
  • getError(): Returns the error information of the errored Workflow instance.

  Example:

  // First wait for the workflow instance to complete:
  await expect(
  	instance.waitForStatus({ status: "complete" })
  ).resolves.not.toThrow();
  
  // Then, get its output
  const output = await instance.getOutput();
  
  // Or for errored workflow instances, get their error:
  await expect(
  	instance.waitForStatus({ status: "errored" })
  ).resolves.not.toThrow();
  const error = await instance.getError();