Minor Changes

• #14490 75d8cb0 Thanks @petebacondarwin! - Add wrangler ai-search jobs commands for managing AI Search indexing jobs

  You can now list, trigger, inspect, cancel, and read the logs of indexing jobs for an AI Search instance:

  wrangler ai-search jobs list <instance>
  wrangler ai-search jobs create <instance> --description "manual reindex"
  wrangler ai-search jobs get <instance> <job-id>
  wrangler ai-search jobs cancel <instance> <job-id>
  wrangler ai-search jobs logs <instance> <job-id>
  

  All commands accept --namespace/-n (defaults to default). All commands except cancel also accept --json for clean machine-readable output.

• #14490 75d8cb0 Thanks @petebacondarwin! - Add --source-jurisdiction to wrangler ai-search create for R2-backed instances

  R2 buckets can live in a specific jurisdiction (for example eu or fedramp). You can now point an AI Search instance at a bucket in one of those jurisdictions:

  wrangler ai-search create my-instance --type r2 --source my-bucket --source-jurisdiction eu

  When run interactively, the R2 source flow also prompts for a jurisdiction and lists (and can create) buckets within it. The value is a free-form string forwarded to the API as source_params.r2_jurisdiction (server-side validated); omit the flag for no specific jurisdiction. This AI Search command is in open beta.

• #14490 75d8cb0 Thanks @petebacondarwin! - Add auth profiles for managing multiple OAuth logins

  Auth profiles let you maintain separate OAuth logins and bind them to directories, so you can switch between different accounts for different projects without having to re-login.

  For example:

  wrangler auth create work
  wrangler auth activate work ~/projects/work
  
  wrangler auth create personal
  wrangler auth activate personal ~/projects/personal

  New commands under wrangler auth:

  • wrangler auth create <name> — create or re-authenticate a named profile via OAuth
  • wrangler auth delete <name> — delete a profile and all its directory bindings
  • wrangler auth activate <name> [dir] — bind a profile to a directory (defaults to cwd). Sub-directories will inherit this profile.
  • wrangler auth deactivate [dir] — remove a directory binding
  • wrangler auth list — list all profiles and their corresponding directories

  There is also a new global --profile flag, which you can use to activate a profile for just that command run. Note that if you have CLOUDFLARE_API_TOKEN set, that will still take precedence over all profiles. Any account id settings (via CLOUDFLARE_ACCOUNT_ID or wrangler config) will also still be respected.

• #14490 75d8cb0 Thanks @petebacondarwin! - Add --strict flag to wrangler versions upload and improve pre-upload safety checks

  wrangler versions upload now runs the same pre-upload checks as wrangler deploy:

  • When the Worker was last edited via the Cloudflare Dashboard, the local and remote configurations are diffed and you are warned only if the diff is destructive (previously, an unconditional warning was shown).
  • When local configuration values conflict with remote secrets, a warning is shown before proceeding.
  • When deploying workflows that belong to a different Worker, a warning is shown before proceeding.

  The new --strict flag (already available on wrangler deploy) causes wrangler versions upload to abort in non-interactive/CI environments when any of these conflicts are detected, instead of auto-continuing.

• #14490 75d8cb0 Thanks @petebacondarwin! - Add D1 migration setup to createTestHarness() Worker handles

  Tests using createTestHarness() can now apply local D1 migrations before running requests:

  const worker = server.getWorker();
  
  beforeEach(async () => {
    await worker.applyD1Migrations("DATABASE");
  });

• #14490 75d8cb0 Thanks @petebacondarwin! - Add Workflow introspection to createTestHarness()

  Worker handles can now introspect Workflow bindings by name, allowing tests to disable sleeps, mock step results, and wait for Workflow outcomes. Tests can introspect a known Workflow instance by ID or track instances created after introspection starts.

  const harness = createTestHarness({
  	workers: [{ configPath: "./wrangler.json" }],
  });
  
  const worker = harness.getWorker();
  await using workflow = await worker.introspectWorkflow("MY_WORKFLOW");
  
  await workflow.modifyAll((modifier) =>
  	modifier.disableSleeps([{ name: "wait-for-approval" }])
  );
  
  const response = await worker.fetch("/start-workflow");
  const [instance] = await workflow.get();
  await instance.waitForStatus("complete");

• #14446 e0cc2cb Thanks @edmundhung! - Add bindingOverrides and getExport() to createTestHarness()

  Test harness workers loaded from Wrangler config files can now replace a configured binding with a Worker in the same harness. This is useful for replacing platform bindings with test Workers while keeping the source Worker config production-like. You can also call getExport() on a Worker returned by server.getWorker(name) to access JSRPC methods on the default Worker export, including mock Workers used as override targets.

  const server = createTestHarness({
    workers: [
      {
        configPath: "./workers/app/wrangler.jsonc",
        bindingOverrides: { BROWSER: "mock-browser" },
      },
      {
        // A mock Worker implementing the Browser Rendering binding named "mock-browser".
        configPath: "./workers/mock-browser/wrangler.jsonc",
      },
    ],
  });
  
  const mockBrowser = await server
    .getWorker<WebEnv, typeof import("./workers/mock-browser")>("mock-browser")
    .getExport();
  await mockBrowser.setScreenshot(stubPng);
  
  const response = await server.fetch("/reports/2026-05-29.png");
  expect(await response.bytes()).toEqual(stubPng);

• #14490 75d8cb0 Thanks @petebacondarwin! - Improve wrangler tail resilience and shutdown behaviour

  wrangler tail previously crashed with a raw stack trace when the keep-alive ping to the Worker timed out, and could exit with an ugly error on Ctrl-C.

  • Errors now flow through wrangler's usual error pipeline instead of escaping as uncaught exceptions.
  • The keep-alive timeout message now clearly explains what happened and no longer prints a stack trace.
  • When the tail connection drops unexpectedly, wrangler tail now automatically tries to reconnect with exponential back-off (up to 5 retries).
  • Ctrl-C now prints a short "Stopping tail..." message (in pretty mode), awaits the server-side tail deletion, and exits cleanly with code 0.

Patch Changes

• #14490 75d8cb0 Thanks @petebacondarwin! - Update dependencies of "miniflare", "wrangler"

  The following dependency versions have been updated:

  Dependency	From	To
  workerd	1.20260625.1	1.20260629.1

• #14478 f10d4ad Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

  The following dependency versions have been updated:

  Dependency	From	To
  workerd	1.20260629.1	1.20260630.1

• #14490 75d8cb0 Thanks @petebacondarwin! - Improve the deploy warning shown when a Workflow name already belongs to another Worker

  The warning still notes that deploying reassigns the workflow to the current Worker, and now also explains why this happens (workflow names must be unique per account) and how to resolve it (rename the workflow in the Wrangler config).

• #14490 75d8cb0 Thanks @petebacondarwin! - use stream instead of deprecated pipeline key ...

Patch Changes

• #14490 75d8cb0 Thanks @petebacondarwin! - Update dependencies of "miniflare", "wrangler"

  The following dependency versions have been updated:

  Dependency	From	To
  workerd	1.20260625.1	1.20260629.1

• #14478 f10d4ad Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

  The following dependency versions have been updated:

  Dependency	From	To
  workerd	1.20260629.1	1.20260630.1

• #14490 75d8cb0 Thanks @petebacondarwin! - Fix edge cases on the local R2 public bucket endpoint (/cdn-cgi/local/r2/public) to match r2.dev: write methods are rejected with 401, malformed/multiple/inverted ranges with 400 and unsatisfiable ranges (including bytes=-0) with 416, Range is honored on HEAD requests with a bodyless 206, Content-Range is correct for suffix ranges, object keys are percent-decoded exactly once (keys containing a literal % no longer fail), and objects stored without a content type are served as application/octet-stream instead of omitting the Content-Type header. Unread object bodies are also cancelled (on HEAD and unsatisfiable-range responses) instead of leaking a read stream until garbage collection.

• #14490 75d8cb0 Thanks @petebacondarwin! - Add Workflow introspection to createTestHarness()

  Worker handles can now introspect Workflow bindings by name, allowing tests to disable sleeps, mock step results, and wait for Workflow outcomes. Tests can introspect a known Workflow instance by ID or track instances created after introspection starts.

  const harness = createTestHarness({
  	workers: [{ configPath: "./wrangler.json" }],
  });
  
  const worker = harness.getWorker();
  await using workflow = await worker.introspectWorkflow("MY_WORKFLOW");
  
  await workflow.modifyAll((modifier) =>
  	modifier.disableSleeps([{ name: "wait-for-approval" }])
  );
  
  const response = await worker.fetch("/start-workflow");
  const [instance] = await workflow.get();
  await instance.waitForStatus("complete");

Patch Changes

• #14490 75d8cb0 Thanks @petebacondarwin! - Update dependencies of "create-cloudflare"

  The following dependency versions have been updated:

  Dependency	From	To
  create-vike	0.0.654	0.0.660

• #14490 75d8cb0 Thanks @petebacondarwin! - Update dependencies of "create-cloudflare"

  The following dependency versions have been updated:

  Dependency	From	To
  nuxi	3.35.2	3.36.1

• #14490 75d8cb0 Thanks @petebacondarwin! - Update dependencies of "create-cloudflare"

  The following dependency versions have been updated:

  Dependency	From	To
  create-vite	9.0.7	9.1.0

• #14490 75d8cb0 Thanks @petebacondarwin! - Update dependencies of "create-cloudflare"

  The following dependency versions have been updated:

  Dependency	From	To
  @tanstack/cli	0.69.3	0.69.5

• #14490 75d8cb0 Thanks @petebacondarwin! - Update dependencies of "create-cloudflare"

  The following dependency versions have been updated:

  Dependency	From	To
  @angular/create	22.0.3	22.0.4

• #14490 75d8cb0 Thanks @petebacondarwin! - Update dependencies of "create-cloudflare"

  The following dependency versions have been updated:

  Dependency	From	To
  create-astro	5.0.6	5.2.0

• #14490 75d8cb0 Thanks @petebacondarwin! - Update dependencies of "create-cloudflare"

  The following dependency versions have been updated:

  Dependency	From	To
  create-analog	2.6.1	2.6.2

• #14490 75d8cb0 Thanks @petebacondarwin! - Fix npm installs for Analog projects

  Analog's generated Vite overrides can cause npm to fail with Unable to resolve reference $vite when dependency resolution changes. create-cloudflare now opts npm-generated Analog projects out of those overrides so project creation can complete successfully.

Minor Changes

• #14490 75d8cb0 Thanks @petebacondarwin! - Make Workflow introspector get() async

  The introspectWorkflow(...).get() method now returns a promise, so callers must await it:

  const introspector = await introspectWorkflow(env.MY_WORKFLOW);
  
  // Before
  const instances = introspector.get();
  
  // After
  const instances = await introspector.get();

  This aligns Workflow introspection with the shared implementation used by createTestHarness().

Patch Changes

• #14490 75d8cb0 Thanks @petebacondarwin! - Support require("./x.wasm?module") in CommonJS dependencies

  Previously, only literal await import("./x.wasm?module") specifiers were rewritten through the static analysis path added in #11094. CommonJS dependencies that use require("./x.wasm?module") reach the module-fallback service at runtime, where the ?module suffix went unhandled. The fallback either failed with No such module "<abs>/x.wasm?module" or, when a CompiledWasm rule was configured, attempted to evaluate the WebAssembly bytes as JavaScript.

  However, these require()s work in deployed workers because esbuild's bundler statically rewrites these require() calls into ES dynamic imports. vitest-pool-workers' Vite-based pipeline doesn't do that rewrite and instead defers to the module-fallback at runtime.

  The module-fallback now strips ?module from the resolved target and synthesizes a CommonJS wrapper that re-requires the underlying .wasm by absolute path, exposing it on default to match what workerd produces for CompiledWasm modules.

• Updated dependencies [75d8cb0, 75d8cb0, 75d8cb0, 75d8cb0, 75d8cb0, f10d4ad, 75d8cb0, 75d8cb0, 75d8cb0, 75d8cb0, d292046, 75d8cb0, 75d8cb0, 75d8cb0, 75d8cb0, 75d8cb0, 75d8cb0, e0cc2cb, 75d8cb0, 75d8cb0, 75d8cb0]:

  • wrangler@4.106.0
  • miniflare@4.20260630.0

Patch Changes

• #14490 75d8cb0 Thanks @petebacondarwin! - Preserve D1 migration paths in generated Worker configs

  When a Worker config with a D1 binding is built by the Vite plugin, the generated wrangler.json now points migrations_dir back to the source migration directory. This lets tools that read the generated config, such as createTestHarness(), find the same D1 migrations as the source Worker config.

• Updated dependencies [75d8cb0, 75d8cb0, 75d8cb0, 75d8cb0, 75d8cb0, f10d4ad, 75d8cb0, 75d8cb0, 75d8cb0, 75d8cb0, d292046, 75d8cb0, 75d8cb0, 75d8cb0, 75d8cb0, 75d8cb0, 75d8cb0, e0cc2cb, 75d8cb0, 75d8cb0, 75d8cb0]:

  • wrangler@4.106.0
  • miniflare@4.20260630.0

Patch Changes

• Updated dependencies [75d8cb0, f10d4ad, 75d8cb0, 75d8cb0]:
  • miniflare@4.20260630.0

Patch Changes

• #14490 75d8cb0 Thanks @petebacondarwin! - remove skipLastDeployedFromApiCheck

  This was a temporary option to bypass an API issue, which has been fixed API side.

• Updated dependencies [75d8cb0, f10d4ad, 75d8cb0, 75d8cb0]:

  • miniflare@4.20260630.0

Minor Changes

• #14311 34e0cef Thanks @sherryliu-lsy! - Add Google Artifact Registry support to containers registries configure

  wrangler containers registries configure now recognizes *-docker.pkg.dev (Google Artifact Registry) domains.

  • The Google service account email is the public credential, supplied with --gar-email. It must match the client_email in the service account key.
  • The service account JSON key is the private credential. It is provided via stdin (a file path, raw JSON, or base64) or an interactive prompt (a file path or base64) — never as a CLI flag, so it does not appear in shell history. The key is validated against --gar-email and stored base64-encoded.
  • Secret reuse inherits the existence-first flow: when the target Secrets Store secret already exists, it is reused by reference and the key is not required. In that case the email cannot be verified locally; it is validated against the key when images are pulled.

  <path-to-key>.json | npx wrangler@latest containers registries configure <region>-docker.pkg.dev --gar-email=<service-account-email> --secret-name=Google_Service_Account_JSON_Key

Patch Changes

• #14424 5f40dd5 Thanks @MattieTK! - Bump am-i-vibing from 0.4.0 to 0.5.0

  This updates the agentic environment detection library to the latest version, which adds detection for the Pi coding agent (earendil-works/pi).

• #14406 3b743c1 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

  The following dependency versions have been updated:

  Dependency	From	To
  workerd	1.20260623.1	1.20260625.1

• #14343 daa5389 Thanks @th0m! - Use digest-pinned image references for Dockerfile container deploys

  Dockerfile-backed container deploys now use the pushed image digest when deploying the container application. This lets snapshot-enabled container apps pass Cloudchamber validation while keeping local, non-pushed builds and registry image URI deploys unchanged.

• #14394 8a5cf8c Thanks @Partha-Shankar! - fix(d1): escape migrationsTableName and filenames in SQLite queries

  D1 migration commands in both wrangler and @cloudflare/vitest-pool-workers interpolated the migrationsTableName config value and migration filenames directly into SQL strings without any escaping. This meant:

  • A table name such as my"table would produce invalid SQL in CREATE TABLE, SELECT, and INSERT statements, and
  • A migration filename containing an apostrophe (e.g. what's-new.sql) would break the INSERT INTO ... VALUES ('...') statement appended after each migration in wrangler.

  Both identifiers are now properly escaped before interpolation: migrationsTableName is wrapped in double-quotes with internal double-quotes doubled (SQL-standard identifier quoting), and migration filenames used as string literals have their single-quotes doubled before insertion.

• Updated dependencies [3b743c1]:

  • miniflare@4.20260625.0

Patch Changes

• #14406 3b743c1 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

  The following dependency versions have been updated:

  Dependency	From	To
  workerd	1.20260623.1	1.20260625.1

Patch Changes

• #14398 c5014cc Thanks @apeacock1991! - Add evictDurableObject and evictAllDurableObjects test helpers to cloudflare:test

  These helpers let you exercise how a Durable Object behaves across evictions in your tests. Eviction is graceful: durable storage is preserved, in-memory state is reset by tearing down the instance, hibernatable WebSockets are hibernated rather than closed, and eviction waits for in-flight requests to drain.

  import { evictDurableObject, evictAllDurableObjects } from "cloudflare:test";
  import { env } from "cloudflare:workers";
  
  const id = env.COUNTER.idFromName("my-counter");
  const stub = env.COUNTER.get(id);
  
  // Evict the Durable Object instance pointed to by a specific stub
  await evictDurableObject(stub);
  await evictDurableObject(stub, { webSockets: "close" });
  
  // Evict all currently-running Durable Objects in evictable namespaces
  await evictAllDurableObjects();

• #14394 8a5cf8c Thanks @Partha-Shankar! - fix(d1): escape migrationsTableName and filenames in SQLite queries

  D1 migration commands in both wrangler and @cloudflare/vitest-pool-workers interpolated the migrationsTableName config value and migration filenames directly into SQL strings without any escaping. This meant:

  • A table name such as my"table would produce invalid SQL in CREATE TABLE, SELECT, and INSERT statements, and
  • A migration filename containing an apostrophe (e.g. what's-new.sql) would break the INSERT INTO ... VALUES ('...') statement appended after each migration in wrangler.

  Both identifiers are now properly escaped before interpolation: migrationsTableName is wrapped in double-quotes with internal double-quotes doubled (SQL-standard identifier quoting), and migration filenames used as string literals have their single-quotes doubled before insertion.

• Updated dependencies [5f40dd5, 34e0cef, 3b743c1, daa5389, 8a5cf8c]:

  • wrangler@4.105.0
  • miniflare@4.20260625.0