Version Packages (beta)

[ant-release-bot]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

main is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on main.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

cf@1.0.0-beta.15

Minor Changes

• 579a3b0: Fail destructive commands when noninteractive confirmation is unavailable

  Breaking change during the beta: destructive commands invoked without a terminal
  or in CI now exit with status 1 when --force is omitted, instead of reporting
  success after aborting. The command still prints confirmation guidance and makes
  no mutation request. Interactive declines retain their existing exit behavior.

• 22f028d: Update the generated command surface and vendored Forge packages for
  Forge OpenAPI release 0adf409896a721b233f4fb9fe61655d34ebb166c.

• baab474: Update the generated command surface and vendored Forge packages for
  Forge OpenAPI release 3a9c5f0fb42a5ce4e8c09b78a19f6f003a2ee7c8.

• 909e52e: Update the generated command surface and vendored Forge packages for
  Forge OpenAPI release 3fad73eb27c381031c09ccdfa28ef9352029cd5a.

• 8be54f5: Update the generated command surface and vendored Forge packages for
  Forge OpenAPI release af1cbe5ccd4d92c232d8cd9c10a42a49e276238c.

Patch Changes

• 51b8cef: Format the account-selection config hint consistently

  After you pick an account, the tip for making it the project's default now
  joins the prompt's guide, wraps to the terminal width, and keeps its snippet
  free of guide characters so it copies cleanly. When the project already has a
  cloudflare.config.ts, the tip names that file and shows only the accountId
  line to add. --quiet now omits the tip.

• a71dd9b: Reject unsupported persistence-directory overrides in cf dev

  cf dev --persist-to <dir> now reports that the option is unsupported instead of
  silently ignoring it. The validation runs before project setup or dev-server
  startup, while cf dev --help remains available with the option present.

• 8747bd9: Allow long-running API operations to finish

  Increase the default API request timeout from 30 to 60 seconds so Workers
  profiling captures can run for the full supported 50 seconds and return their
  results. Apply the same default to SDK and raw-response requests while retaining
  explicit timeout overrides and the exemption for binary and multipart uploads.

• 327cb9f: Use the configured project's commands on the first cf dev or cf build after setup

  When cf dev or cf build set up a project, they kept the commands and environment detected before setup. If setup changes the project's tooling, for example by setting up a Next.js project with vinext, the first run would use the old commands. cf now analyses the project again after setup, as it already did after converting a Wrangler config.

[pkg-pr-new]

npm i https://pkg.pr.new/cf@253

commit: 83c44fe

[github-actions]

cf --help startup

	mean	stddev	min	max
PR	225.3 ms	5.0 ms	218.0 ms	237.8 ms
base	225.6 ms	4.9 ms	217.2 ms	238.4 ms

Δ (PR vs base): — -0.3 ms (-0.1%)

Measured with hyperfine on ubuntu-latest (3 warmup runs, 20 timed runs). CI numbers carry ±a few ms of runner jitter; treat small deltas as noise.