Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .changeset/pre.json
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,9 @@
"cuddly-rivers-shine",
"deploy-worker-flag",
"detect-migrate-bundler",
"durable-object-container-ssh",
"first-public-beta",
"global-boolean-values",
"load-cloudflare-dotenv",
"migrate-before-autoconfig",
"narrow-sdk-error-imports",
Expand Down
19 changes: 19 additions & 0 deletions packages/cli/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,17 @@
# cf

## 1.0.0-beta.12

### Patch Changes

- 2aea37c: Deploy SSH settings for Durable Object-managed Containers

`cf deploy` now forwards a Durable Object-managed Container's `ssh` and `authorizedKeys` from Build Output to the Containers API.

- 8c55fb3: Recognize explicit boolean values before commands

When a global boolean flag or alias is followed by `true` or `false`, treat the literal as its value while identifying the command. This keeps invocations such as `cf --local false complete bash` from receiving the wrong startup behavior.

## 1.0.0-beta.11

### Patch Changes
Expand Down Expand Up @@ -98,6 +110,7 @@
`cf migrate` now uses the Vite bundler only when `@cloudflare/vite-plugin` is declared next to the Wrangler configuration, and uses the Wrangler bundler otherwise. Previously, every project defaulted to Vite, so migrations of non-Vite Workers reported Vite-only follow-ups even though `cf build` would continue to use Wrangler. Pass `--bundler vite` or `--bundler wrangler` to choose explicitly.

- b4112c2: Allow `cf` commands to use these variables from `.env` files:

- `CLOUDFLARE_ACCESS_CLIENT_ID`
- `CLOUDFLARE_ACCESS_CLIENT_SECRET`
- `CLOUDFLARE_ACCOUNT_ID`
Expand Down Expand Up @@ -376,6 +389,7 @@
### Minor Changes

- 5aa6d11: Add Container build, push, and deploy workflows

- `cf containers build <path> --tag <name:tag> [--push]`
- `cf containers push --tag <name:tag>`
- `cf deploy [--containers-rollout immediate|gradual|none]`
Expand Down Expand Up @@ -549,6 +563,7 @@ workers check`, and `cf workers triggers deploy` to consume the latest Build

The command now fetches the extension's schema
(`GET /registrar/extensions/{name}`) and drives itself from it:

- The domain is a positional: `cf registrar registrations create example.travel`.
Its extension is derived from the name (longest suffix first, so `co.uk` beats
`uk`), or set explicitly with `--extension`.
Expand Down Expand Up @@ -615,6 +630,7 @@ workers check`, and `cf workers triggers deploy` to consume the latest Build

Closes the gap that kept migrated repos on a `wrangler.jsonc` and a `wrangler`
devDependency for one job. Three subcommands:

- `cf d1 migrations apply <database>` — apply every unapplied migration
- `cf d1 migrations list <database>` — report unapplied migrations as JSON
- `cf d1 migrations create <message>` — scaffold a numbered migration file
Expand Down Expand Up @@ -697,6 +713,7 @@ create`) type a field the schema says nothing about — `{}`, as Workers AI
(`--text`, `--prompt`, `--guidance`, …) — accurate for none of them. `cf ai run`
is now hand-written and reads the chosen model's input schema from
`/ai/models/schema` at run time:

- `cf ai run <model> --help` lists **that model's** fields, with types, defaults
and enum choices. `cf ai run --help` on its own makes no network request.
- Input is validated against the model's schema before the request goes out, so
Expand Down Expand Up @@ -886,6 +903,7 @@ create`) type a field the schema says nothing about — `{}`, as Workers AI
(PKCE flow, callback server, token refresh) instead of cf's own implementation,
while keeping cf's own OAuth identity (client ID and consent pages). Notable
changes:

- Tokens are now stored as JSONC in cf's XDG-compliant config directory (e.g.
`~/.config/.cf/auth.jsonc`) instead of `~/.cf/config.toml`. You will need to
run `cf auth login` once to re-authenticate.
Expand Down Expand Up @@ -920,6 +938,7 @@ create`) type a field the schema says nothing about — `{}`, as Workers AI
- 11ad38d: Drop client-side input "hardening"

cf no longer pre-validates user input before sending it to the API:

- **Path params / string positionals.** Generated commands previously
ran `validateResourceId` / `validateStringInput` to reject `..`, URL
operators (`?` `#` `%`), and control characters. These are gone.
Expand Down
2 changes: 1 addition & 1 deletion packages/cli/package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "cf",
"version": "1.0.0-beta.11",
"version": "1.0.0-beta.12",
"description": "The Cloudflare CLI",
"keywords": [
"ai",
Expand Down
Loading