PuppyIP Resource Center
Developer Tools & Networking 5 min Published 2026-11-18

Cloudflare CLI 1.0 RC: Upgrade from Beta with Build Output v1

Before trying Cloudflare CLI 1.0.0-rc.1 from beta, check your build dependencies and pipeline. Build Output now goes to .cloudflare/output/v1/, with different minimum dependencies for Vite and older Wrangler projects. Test the release candidate on an isolated project and follow your project's release process before going live.

Cloudflare CLI Build Output Wrangler Vite CI

Service eligibility and regional restrictions

PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.

Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.

Key Takeaways

  • Cloudflare announced release candidate 1.0.0-rc.1 on November 17, 2026. Some generated API commands can still change before 1.0.
  • Vite builds need @cloudflare/vite-plugin 2.0.0-rc.0 or newer. Legacy Wrangler builds need Wrangler 4.163.0 or newer.
  • If you are coming from an early beta, check the preview-name flag and output streams. Command output goes to stdout, and prompts and progress go to stderr.

Who should try this release candidate?

This upgrade primarily affects teams already using cf beta, especially Workers projects with separate build and deploy stages. Record your current CLI, Node.js, and project dependency versions on an isolated branch before testing 1.0.0-rc.1. Cloudflare lists configuration and common commands it expects to remain stable, while some less common API commands can still change.

If your project runs Wrangler directly today, first check whether your team plans to try cf. The Wrangler minimum in this announcement applies to the build path where cf delegates to Wrangler.

What changes for build artifacts and dependencies?

The new Build Output directory is .cloudflare/output/v1/. Cloudflare says cf deploy creates a new build in that location on its first run. Check your CI cache, artifact upload, and downstream readers so they use the same directory and dependency versions.

Identify the builder before checking the minimum version. Vite projects need @cloudflare/vite-plugin 2.0.0-rc.0 or newer. Legacy projects built with Wrangler need Wrangler 4.163.0 or newer. Record the dependency versions you test so you can reproduce or roll back the change.

Why might an older script read the wrong output?

If you are upgrading from an early beta, check that your script reads command output from stdout and prompts, progress, and status from stderr. For example, a script that parses stdout as JSON should capture progress separately to avoid breaking the parser.

Pass the preview name with --preview-name in cf previews deploy. Review generated command names and flags too. Cloudflare says some renamed commands have no aliases. Check the help for the installed version before changing your scripts.

How can you verify the upgrade and keep a rollback path?

Start with a reproducible local build, confirm it writes to v1, and check the downstream stages that read the artifacts. In an approved test environment, verify the target account, preview name, output parsing, and exit status. Record the previous CLI, lockfile, and working artifacts before planning the production change.

Use the documented cf deploy --dry-run preview to inspect the proposed deployment changes. Review the preview and follow the actual change process for the target environment before switching over.

Sources

Frequently Asked Questions

Can I rename the old Build Output directory to v1?

v1 identifies a build artifact format. Upgrade the relevant dependencies, regenerate the artifacts, and point downstream steps to v1. Renaming a directory does not validate its contents.

Do older beta command names still work after I change the CLI version?

Cloudflare says some generated commands were renamed without aliases. Check the current help and release notes for every command your project calls.