ReleaseCloudflare (Workers AI)Cloudflare (Workers AI)published Jun 5, 2026seen 5d

cloudflare/workers-sdk @cloudflare/workers-utils@0.23.0

cloudflare/workers-sdk

Open original ↗

Captured source

source ↗
published Jun 5, 2026seen 5dcaptured 12hhttp 200method plain

@cloudflare/workers-utils@0.23.0

Repository: cloudflare/workers-sdk

Tag: @cloudflare/workers-utils@0.23.0

Published: 2026-06-05T10:47:42Z

Prerelease: no

Release notes:

Minor Changes

The D1 binding now accepts an optional migrations_pattern field, allowing you to point wrangler d1 migrations apply and wrangler d1 migrations list at migration files in nested layouts (e.g. ORM-generated folders like migrations/0000_init/migration.sql).

migrations_pattern is a glob (relative to the wrangler config file) and defaults to ${migrations_dir}/*.sql, which preserves today's behaviour. Files that do not match the pattern are not executed.

{
"d1_databases": [
{
"binding": "DB",
"database_name": "my-db",
"database_id": "...",
"migrations_dir": "migrations",
"migrations_pattern": "migrations/*/migration.sql"
}
]
}

When no migrations match the configured pattern but files matching the common migrations/*/migration.sql (drizzle-style) layout do exist, Wrangler logs a hint suggesting migrations_pattern as an opt-in.

wrangler d1 migrations create now returns an actionable error if the generated migration filename would not match the configured pattern.

Pre-launch rename of the public binding type from web_search to websearch so the on-the-wire shape matches the product name (Web Search). The wrangler config key, the binding-type string sent to the Cloudflare API, and the miniflare option key all move from web_search / webSearch to websearch.

Update your wrangler config:

- "web_search": { "binding": "WEBSEARCH" }
+ "websearch": { "binding": "WEBSEARCH" }

The runtime WebSearch type exposed on env.WEBSEARCH is unchanged.

The constructWranglerConfig function now accepts a single APIWorkerConfig object instead of APIWorkerConfig | APIWorkerConfig[]. The multi-environment array support has been removed since the array use-case was removed and now the only call site already passes a single worker object. This is a breaking change to the function's public signature.

Notability

notability 2.0/10

Routine version bump release