cloudflare/cf cf@1.0.0-beta.21

cf@1.0.0-beta.21

Repository: cloudflare/cf

Tag: cf@1.0.0-beta.21

Published: 2026-10-23T11:50:15Z

Prerelease: no

Release notes:

Minor Changes

• dcab54d: Move prompts, progress and workflow messages to stderr

Breaking change during the beta: prompts, confirmations and the progress spinner now render on stderr, so they keep working while stdout is redirected, as in cf kv namespaces create > ns.json, and a confirmation that used to fail there now waits for an answer. Some confirmations in cf deploy and cf workers triggers deploy still ask only when stdout is a terminal, and go ahead without asking otherwise. Prompts and the spinner need stdin and stderr to be terminals outside CI, so the spinner no longer swallows piped input, and Ctrl+C or Esc during the spinner now exits with status 130 instead of 0. cf init, cf build, cf deploy, cf workers versions create and cf workers triggers deploy print their messages on stderr too, together with the output of the build and install commands cf runs, so scripts that read those messages from stdout must read stderr instead. cf previews deploy no longer prints upload messages into its JSON output, and cf dev still gives the dev server the whole terminal.

--quiet now also hides notices and the ✓ success line, but never warnings, the commands that fix them, or prompts. A declined delete ends with └ Aborted., cf init prints its next steps below the closed flow so each copies on its own, the first-run notices use clack info lines, and the dev-server errors use the error frame with each install command on its own line.

• c440926: Record the global cf version in telemetry when it delegates to a project-pinned cf

When a globally installed cf hands a command to the copy a project pins, it now passes its own version to that copy, which adds it to telemetry as globalCliVersion. cliVersion remains the version of the cf that runs the command, and delegated still marks delegated runs. Older global installs do not pass a version, so the property is omitted for them.

• b50a51a: Record sanitised detail about unrecognised commands in usage telemetry

When cf cannot match the arguments to a command, telemetry now records the kind of failure, the recognised part of the command path, whether that part is a complete command, and up to three unrecognised words. Only the first word can be included as written, and only when it is a cf command name in a place where a command name was expected; later words and anything else, including any extra value after a complete command, are replaced by a category such as `, , or . Unrecognised flags, including short flags such as -x`, are counted, never named.

Failures inside a group or command keep the command value they were reported under before. Failures at the top level that were previously dropped – a typo with a suggestion, several unknown words, or only flags with no command – are now reported as unknown commands.

• c761c0e: Update the generated command surface for Forge OpenAPI release

2d3b9ab6825d7087ebe00a4b03c2ff219f08e4b4.

• af49ab3: Update the generated command surface for Forge OpenAPI release

536d02b4bd5629be5333aea4cf1024680abac1ef.

• 4f7b6b4: Update the generated command surface for Forge OpenAPI release

5de500b2959b09d00972516cac5a6c56aec4878a.

• 9b339a6: Update the generated command surface for Forge OpenAPI release

880ff24a8d487f05651f6dc24f482b9845127c7f.

• 8e51747: Update the generated command surface for Forge OpenAPI release

acc1cbed2ca3136244a31aee12f25fc6164566cc.

• 25ad929: Update the generated command surface for Forge OpenAPI release

fdbc7d9b0fdce613501dd81cb37466fbaf0b7cca.

Patch Changes

• 09c9303: Update dependencies published from the Workers SDK repository:

• @cloudflare/autoconfig: 0.7.11 → 0.8.0
• @cloudflare/build-output-utils: 0.9.3 → 0.9.4
• @cloudflare/cli-shared-helpers: 0.2.7 → 0.2.8
• @cloudflare/codemods: 0.5.1 → 0.6.0
• @cloudflare/config: 0.27.0 → 0.28.0
• @cloudflare/containers-shared: 0.23.1 → 0.23.2
• @cloudflare/deploy-helpers: 0.22.1 → 0.23.0
• @cloudflare/runtime-types: 0.1.14 → 0.1.15
• @cloudflare/workers-auth: 0.14.1 → 0.15.0
• @cloudflare/workers-utils: 0.47.3 → 0.48.0
• miniflare: 5.20261019.1-beta → 5.20261019.2-beta

• d4a5d17: Skip reading the compliance region from the config file when it is set in the environment

Resolve CLOUDFLARE_COMPLIANCE_REGION before project settings, matching the existing account ID priority. Commands with both CLOUDFLARE_ACCOUNT_ID and CLOUDFLARE_COMPLIANCE_REGION no longer evaluate a cloudflare.config.ts file solely to establish API context.