#12435 c2163df Thanks @petebacondarwin! - Simplify Version Packages PR CI failure alerts
The bot now sends an alert for any failing CI job on the Version Packages PR, instead of first fetching the required status checks from GitHub's branch protection API and filtering. This removes unnecessary complexity and ensures all CI failures are reported.
2acb277 Thanks @martinezjandrew! - Updated registries delete subcommand to handle new API response that now returns a secrets store secret reference after deletion. Wrangler will now prompt the user if they want to delete the associated secret. If so, added new logic to retrieve a secret by its name. The subcommand will then delete the secret.#12467 7036310 Thanks @petebacondarwin! - Add support for inline comments in _redirects files
You can now add inline comments to redirect rules using the # character:
/old-page /new-page 301 # Moved during site redesign
/blog/* /articles/:splat # Blog URL migration
This improves the maintainability of _redirects files by allowing documentation of complex redirect rules directly alongside the rules themselves. Full-line comments (lines starting with #) continue to work as before. URL fragments (e.g., /page#section) are preserved correctly.
#12377 312b5eb Thanks @vicb! - Use the native node:process v2 when it is available
Note that we only enable this if all of the following conditions are met:
fetch_iterable_type_support and fetch_iterable_type_support_override_adjustment are active (explicitly specified or implied by date or other flags).Note that EventEmitters (on, off, addListener, removeListener, ...) used to be available on the imported process module while they should not have been. They are now only available on the global process:
import p from "node:process";
// Working before this PR, not working after this PR
p.on("exit", exitHandler);
// Use the global process instead (works before and after the PR)
process.on("exit", exitHandler);#12469 2d90127 Thanks @petebacondarwin! - Add environment variables to control cf.json fetching behavior
You can now use environment variables to control how Miniflare handles the Request.cf object caching:
CLOUDFLARE_CF_FETCH_ENABLED - Set to "false" to disable fetching entirely and use fallback data. No node_modules/.mf/cf.json file will be created. Defaults to "true".CLOUDFLARE_CF_FETCH_PATH - Set to a custom path to use a different location for caching the cf.json file instead of the default node_modules/.mf/cf.json.This is particularly useful for non-JavaScript projects (like Rust or Go Workers) that don't want a node_modules directory created automatically.
Example:
# Disable cf fetching for all projects
export CLOUDFLARE_CF_FETCH_ENABLED=false
npx wrangler dev
# Or use a custom cache location
export CLOUDFLARE_CF_FETCH_PATH=/tmp/.cf-cache.json
npx wrangler dev#12391 ce9dc01 Thanks @emily-shen! - Serve the local explorer UI from Miniflare
This bundles the local explorer UI into Miniflare, and if enabled, Miniflare serves the UI at /cdn-cgi/explorer.
This is an experimental, WIP feature.
#12440 555b32a Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| workerd | 1.20260205.0 | 1.20260206.0 |
#12485 d636d6a Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| workerd | 1.20260206.0 | 1.20260207.0 |
#12502 bf8df0c Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| workerd | 1.20260207.0 | 1.20260210.0 |
#12286 5ddd276 Thanks @elithrar! - Add AGENTS.md to Workers templates for AI coding agent guidance
New Workers projects created via create-cloudflare now include an AGENTS.md file that provides AI coding agents with retrieval-led guidance for Cloudflare APIs. This helps agents avoid using outdated knowledge from their training data and instead consult current documentation.
The file includes:
dev, deploy, types)#12454 c99c437 Thanks @petebacondarwin! - Respect CLOUDFLARE_ACCOUNT_ID environment variable for account selection
When the CLOUDFLARE_ACCOUNT_ID environment variable is set, C3 will now use it directly
instead of prompting for account selection. This matches wrangler's behavior and enables
seamless CI/CD workflows where the account is pre-configured via environment variables.
Previously, C3 would always call wrangler whoami and prompt for account selection when
multiple accounts were available, ignoring the environment variable.
#12365 9eca052 Thanks @dependabot! - Update dependencies of "create-cloudflare"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| @angular/create | 21.1.1 | 21.1.2 |
#12366 96d1605 Thanks @dependabot! - Update dependencies of "create-cloudflare"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| create-vue | 3.20.0 | 3.21.0 |
#12367 9244501 Thanks @dependabot! - Update dependencies of "create-cloudflare"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| gatsby | 5.15.0 | 5.16.0 |
#12481 0ac76d5 Thanks @dependabot! - Update dependencies of "create-cloudflare"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| create-vike | 0.0.572 | 0.0.575 |
#12381 98283fa Thanks @jamesopstad! - Avoid collecting nodejs_compat warnings during dependency optimization.
Previously, a custom plugin was provided during dependency optimization to collect warnings when Node.js built-ins were imported and the nodejs_compat flag was not enabled.
Because optimized dependencies are cached, the warning was only displayed when dependencies changed.
Additionally, it sometimes included false positives from dependencies that were no longer used.
We now always externalize Node.js built-ins during dependency optimization and collect the warnings at runtime.
This is more consistent with how warnings are collected for direct imports of Node.js built-ins.
Updated dependencies [ee9b81f, 63f1adb, ba13de9, 447daa3, fe3af35, bd4bb98, dab4bc9, 83adb2c, 18c0784]:
#12267 83adb2c Thanks @NuroDev! - Implement local D1 API for experimental/WIP local resource explorer
The following APIs have been implemented:
GET /d1/database - Returns a list of D1 databases.POST /d1/database/{database_id}/raw - Returns the query result rows as arrays rather than objects.#12402 63f1adb Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| workerd | 1.20260131.0 | 1.20260203.0 |
#12418 ba13de9 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| workerd | 1.20260203.0 | 1.20260205.0 |
38ad241 Thanks @WillTaylorDev! - Revert reduced cache TTL. Restore 60-second TTL for KV asset fetches.#12288 60eaf16 Thanks @emily-shen! - Set up local explorer UI with a view for KV namespaces
This is an experimental WIP package.
#12368 bd4bb98 Thanks @KianNH! - Preserve Containers configuration when using versions commands
Previously, commands like wrangler versions upload would inadvertently disable Containers on associated Durable Object namespaces because the containers property was being omitted from the API request body.
#8310 fed18f9 Thanks @irvinebroque! - Enable nodejs_compat by default for new projects
New projects created with C3 will now have the nodejs_compat compatibility flag automatically enabled. This makes it easier to get started with Workers, as many npm packages require Node.js compatibility to work correctly.
If you don't want nodejs_compat enabled, you can remove it from your wrangler.json or wrangler.toml configuration file:
{
"compatibility_flags": []
}#12371 50ad9a9 Thanks @petebacondarwin! - Send alert to ANT: Alerts chat on failed CI checks in Version Packages PRs
When a required CI check fails or times out on the Version Packages PR (changeset-release/main branch), an alert is now sent to the ANT: Alerts Google Chat channel. This helps the team quickly identify and address CI failures that shouldn't occur since individual PRs have already passed before landing on main.
Alerts for the same PR are grouped into the same chat thread using the PR number as the thread ID.
#12386 447daa3 Thanks @NuroDev! - Added new "open local explorer" hotkey for experimental/WIP local resource explorer
When running wrangler dev with the experimental local explorer feature enabled, you can now press the e hotkey to open the local resource explorer UI in your browser.
#11350 ee9b81f Thanks @dario-piotrowicz! - fix: improve error message when the entrypoint is incorrect
Error messages for incorrect entrypoint configuration have been improved to provide clearer and more actionable feedback. The updated messages help users understand what went wrong and how to fix their configuration.
#12402 63f1adb Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| workerd | 1.20260131.0 | 1.20260203.0 |
#12418 ba13de9 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| workerd | 1.20260203.0 | 1.20260205.0 |
#12216 fe3af35 Thanks @ichernetsky-cf! - Deprecate 'wrangler cloudchamber apply' in favor of 'wrangler deploy'
#12368 bd4bb98 Thanks @KianNH! - Preserve Containers configuration when using versions commands
Previously, commands like wrangler versions upload would inadvertently disable Containers on associated Durable Object namespaces because the containers property was being omitted from the API request body.
#12396 dab4bc9 Thanks @petebacondarwin! - fix: redact email addresses and account names in non-interactive mode
To prevent sensitive information from being exposed in public CI logs, email addresses and account names are now redacted when running in non-interactive mode (e.g., CI environments). Account IDs remain visible to aid debugging.
#12378 18c0784 Thanks @X6TXY! - Truncate Pages commit messages at UTF-8 boundaries to avoid invalid UTF-8
Updated dependencies [63f1adb, ba13de9, 83adb2c]:
#12064 964a39d Thanks @G4brym! - Add AI Search OAuth scopes to login
Adds ai-search:write and ai-search:run OAuth scopes to the default login scopes, enabling wrangler to authenticate with AI Search APIs.
#11867 253a85d Thanks @rahulsuresh-git! - Add wrangler r2 bucket local-uploads command to manage local uploads for R2 buckets
When enabled, object data is written to the nearest region first, then asynchronously replicated to the bucket's primary region.
Docs: https://developers.cloudflare.com/r2/buckets/local-uploads
# Get local uploads status
wrangler r2 bucket local-uploads get my-bucket
# Enable local uploads (will prompt for confirmation)
wrangler r2 bucket local-uploads enable my-bucket
# Enable without confirmation prompt
wrangler r2 bucket local-uploads enable my-bucket --force
# Disable local uploads
wrangler r2 bucket local-uploads disable my-bucket#11803 1bd1488 Thanks @dario-piotrowicz! - Add a new subrequests limit to the limits field of the Wrangler configuration file
Before only the cpu_ms limit was supported in the limits field of the Wrangler configuration file, now a subrequests limit can be specified as well which enables the user to limit the number of fetch requests that a Worker's invocation can make.
Example:
{
"$schema": "./node_modules/wrangler/config-schema.json",
"limits": {
"cpu_ms": 1000,
"subrequests": 150 // newly added field
}
}#12185 f7aa8c7 Thanks @penalosa! - Add timestamp field to the version metadata binding in local development. The version metadata binding now includes id, tag, and timestamp fields, making it easier to test version-aware logic locally.
#12190 ce736b9 Thanks @dario-piotrowicz! - Update autoconfig logic to handle Next.js projects by using the new @opennextjs/cloudflare migrate command
#12065 47944d1 Thanks @langningchen! - Improve error message when d1 export --output points to a directory
#12292 4c4d5a5 Thanks @dario-piotrowicz! - Add versionCommand to the autoconfig_summary field in the autoconfig output entry
Add the version upload command to the output being printed by wrangler deploy to WRANGLER_OUTPUT_FILE_DIRECTORY/WRANGLER_OUTPUT_FILE_PATH. This complements the existing buildCommand and deployCommand fields and allows CI systems to know how to upload new versions of Workers.
For example, for a standard npm project this would be:
npx wrangler versions uploadWhile for a Next.js project it would be:
npx @opennextjs/cloudflare upload#12050 b05b919 Thanks @NuroDev! - Fixed Wrangler's error handling for both invalid commands with and without the --help flag, ensuring consistent and clear error messages.
Additionally, it also ensures that if you provide an invalid argument to a valid command, Wrangler will now correctly display that specific commands help menu.
#12289 0aaf080 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| workerd | 1.20260128.0 | 1.20260129.0 |
#12295 b981db5 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| workerd | 1.20260129.0 | 1.20260130.0 |
#12355 a113c0d Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"
The following dependency versions have been updated:
| Dependency | From | To |
|---|---|---|
| workerd | 1.20260130.0 | 1.20260131.0 |
#11971 fdd7a9f Thanks @dario-piotrowicz! - Add framework id, build command, and deploy command to the autoconfig_summary field in the deploy output entry
Add the framework id alongside the commands to build and deploy the project to the output being printed by wrangler deploy to WRANGLER_OUTPUT_FILE_DIRECTORY or WRANGLER_OUTPUT_FILE_PATH.
For example for an npm Astro project these would be:
astronpm run buildnpx wrangler deployWhile for a Next.js project they would instead be:
nextnpx @opennextjs/cloudflare buildnpx @opennextjs/cloudflare deploy#12211 a5fca2c Thanks @elithrar! - Remove the 'pubsub' sub-command and related functionality
The Pub/Sub product was never made publicly available and has been discontinued. This removes the wrangler pubsub command and all associated functionality.
Updated dependencies [0c9625a, 0aaf080, b981db5, a113c0d, f7aa8c7]:
#11803 1bd1488 Thanks @dario-piotrowicz! - Add a new subrequests limit to the limits field of the Wrangler configuration file
Before only the cpu_ms limit was supported in the limits field of the Wrangler configuration file, now a subrequests limit can be specified as well which enables the user to limit the number of fetch requests that a Worker's invocation can make.
Example:
{
"$schema": "./node_modules/wrangler/config-schema.json",
"limits": {
"cpu_ms": 1000,
"subrequests": 150 // newly added field
}
}