cloudflare/workers-sdk wrangler@4.101.0

wrangler@4.101.0

Repository: cloudflare/workers-sdk

Tag: wrangler@4.101.0

Published: 2026-06-16T15:36:57Z

Prerelease: no

Release notes:

Minor Changes

• #14276 `32f9307` Thanks @dario-piotrowicz! - Graduate autoconfig from experimental to stable

The --experimental-autoconfig and --x-autoconfig deploy CLI flags have been replaced with --autoconfig.

Note that the --autoconfig flag defaults to true and that it can be used to disable Wrangler's auto-configuration logic by setting it to false via --autoconfig=false or --no-autoconfig

• #14287 `41f391f` Thanks @edmundhung! - Add per-Worker resource accessors to createTestHarness()

createTestHarness() now provides methods for accessing configured KV namespaces, R2 buckets, D1 databases, and Durable Object namespaces. Use server.getWorker(name) to access resources scoped to that specific Worker:

const worker = server.getWorker("api-worker");
const bucket = await worker.getR2Bucket("BUCKET");
const db = await worker.getD1Database("DB");

• #14264 `21dbc12` Thanks @dario-piotrowicz! - Suggest Cloudflare skills installation after commands instead of before

The automatic prompt to install Cloudflare skills for detected AI coding agents no longer runs before every Wrangler command. Instead, Wrangler now suggests installing skills, when appropriate, after some commands complete successfully. Commands that output JSON suppress the suggestion to keep their output clean. The --install-skills flag remains available on all commands to explicitly run the skills installation flow before the command executes, without prompting.

As before, Wrangler asks the skills installation question at most once. The skills install metadata file is now written before the confirmation prompt is shown, so even if the user interrupts the process (e.g. CTRL+C, closing the terminal) during the prompt, the question is recorded as unanswered and will not reappear on subsequent runs.

• #14042 `7e63948` Thanks @edevil! - Add a --temporary flag that creates and uses a temporary Cloudflare preview account when you have no credentials, instead of starting the OAuth login flow.

It's registered only on the commands the short-lived account token can serve — Workers (deploy, versions upload, and related commands), KV, D1, Hyperdrive, Queues, and certificate commands — and is for unauthenticated use only: passing it while already authenticated (OAuth, CLOUDFLARE_API_TOKEN, or a global API key) errors rather than silently ignoring the flag. Before provisioning, Wrangler handles Cloudflare's Terms of Service and Privacy Policy (interactive terminals prompt for yes; non-interactive shells print a notice and continue). Wrangler then runs with the short-lived token and prints a claim URL so the account can be claimed before it expires. The cached account is cleared on successful login or logout.

• #14299 `035917f` Thanks @petebacondarwin! - Send the login user telemetry event when wrangler login --scopes ... succeeds

wrangler login was already reporting the login user event when called without --scopes, but the scoped login path returned early before the event could be sent. Both paths now report the event, so successful scoped logins are counted alongside unscoped ones.

Patch Changes

• #14271 `27db82c` Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

The following dependency versions have been updated:

| Dependency | From | To | | ---------- | ------------ | ------------ | | workerd | 1.20260611.1 | 1.20260612.1 |

• #14298 `2a6a26b` Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

The following dependency versions have been updated:

| Dependency | From | To | | ---------- | ------------ | ------------ | | workerd | 1.20260612.1 | 1.20260615.1 |

• #14317 `9a424ed` Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

The following dependency versions have been updated:

| Dependency | From | To | | ---------- | ------------ | ------------ | | workerd | 1.20260615.1 | 1.20260616.1 |

• #14282 `ecfdd5a` Thanks @edmundhung! - Fix wrangler dev asset fallback with custom routes

wrangler dev now applies Workers Assets fallback behavior consistently when routes are configured, including SPA fallback and 404-page handling.

• #13763 `604be26` Thanks @matingathani! - Show a clear error when deploying a service-worker format Worker with Durable Object migrations or bindings instead of an opaque API error

• #14240...