Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
18 commits
Select commit Hold shift + click to select a range
9cb1d00
fix(cli): check platform support before deploying database.readReplic…
Brooooooklyn Nov 18, 2026
c9976b8
fix(deps): pin @cloudflare/config and @cloudflare/build-output-utils
Brooooooklyn Nov 18, 2026
227afc3
fix(cli): show the SQL errors D1 reports when a file import fails
Brooooooklyn Nov 18, 2026
7d9cbb7
fix(cli): bound each D1 import request, not the whole import
Brooooooklyn Nov 18, 2026
8a34a12
fix(cli): keep printing rows for small D1 --file SQL
Brooooooklyn Nov 18, 2026
2fc9e39
fix(email): stop re-prompting sending-only apps waiting for Email Sen…
Brooooooklyn Nov 18, 2026
d27e852
docs(email): describe sending-only apps on Workers Free
Brooooooklyn Nov 18, 2026
6336339
fix(init): read the default and Yarn catalogs for the Vite+ bootstrap
Brooooooklyn Nov 18, 2026
4af0ea4
fix(init): list edits outside a new starter app in the summary
Brooooooklyn Nov 18, 2026
29bf2b7
fix(ai): reject a cancelled provider SSE stream with the abort reason
Brooooooklyn Nov 18, 2026
a60a000
test(cli): import a 25 MB SQL file into direct D1 in CI end to end
Brooooooklyn Nov 18, 2026
d9fbe92
feat(cli): add --yes to `void db execute`
Brooooooklyn Nov 18, 2026
cef189b
fix(cli): send LF line endings to the D1 query API
Brooooooklyn Nov 18, 2026
f5a258a
fix(cli): bound the D1 import upload and treat a failed init as unknown
Brooooooklyn Nov 18, 2026
ef8cb2c
test(email): pin the CI output of an onboarded sending-only deploy
Brooooooklyn Nov 18, 2026
a547b44
fix(email): read and onboard sending-only Email Sending on the resolv…
Brooooooklyn Nov 18, 2026
54433bd
fix(cli): keep a non-JSON 4xx D1 import refusal a plain failure
Brooooooklyn Nov 18, 2026
0c631b5
fix(email): name a missing session bearer instead of Workers Paid
Brooooooklyn Nov 18, 2026
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: 1 addition & 1 deletion .agents/skills/void-deps-updates/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ Work in the Void maintainer checkout. Read its current `AGENTS.md`, `packages/vo
- Capture a fresh production-install baseline **before editing**. Build and pack the complete public release cohort, including the platform runtime. Use [the measurement helper](#measure).
- Update direct and transitive dependencies recursively through Vite+. Preserve explicitly held TypeScript/Svelte versions and their framework-specific catalogs; inspect current compatibility constraints rather than freezing historical versions forever.
- Coordinate `cf`, Cloudflare Vite plugin, Wrangler, Miniflare/workerd, and Cloudflare support packages using their actual registry ranges and dist-tags. Dated prereleases need explicit alignment; stable `latest` can be an older major than an intended beta.
- Update the exact pins for `cf`, `@cloudflare/vite-plugin`, and `miniflare` together. Their releases must resolve to the same Miniflare and workerd. Preserve other compatible published ranges, `workspace:*`, strict catalogs, intentional overrides, and package extensions. Avoid forcing incompatible runtime versions. Run `vp dedupe` and inspect remaining outdated packages.
- Update the exact pins for `cf`, `@cloudflare/vite-plugin`, `miniflare`, `@cloudflare/config`, and `@cloudflare/build-output-utils` together. Their releases must resolve to the same Miniflare and workerd. Pin `@cloudflare/config` and `@cloudflare/build-output-utils` to the exact versions that `cf` and the Vite plugin depend on; check with `npm view cf@<version> dependencies` and `npm view @cloudflare/vite-plugin@<version> dependencies`. Preserve other compatible published ranges, `workspace:*`, strict catalogs, intentional overrides, and package extensions. Avoid forcing incompatible runtime versions. Run `vp dedupe` and inspect remaining outdated packages.
- Update `void init`/Vite+ scaffold and bootstrap expectations. Match the React compiler dependency to the installed React plugin's peer range. Keep Sandbox SDK, Docker helper, and verified helper layer aligned.
- Keep prerender architecture changes separate from routine dependency alignment.

Expand Down
3 changes: 3 additions & 0 deletions .github/scripts/packed-consumer.mjs
Original file line number Diff line number Diff line change
Expand Up @@ -389,6 +389,9 @@ for (const name of ['cf', '@cloudflare/vite-plugin']) {
assert.equal(manifest('miniflare', tool), miniflare, name + ' installs a second Miniflare');
assert.equal(manifest('miniflare', types), miniflare, name + ' runtime types install a second Miniflare');
assert.equal(manifest('workerd', types), workerd, name + ' runtime types install a second workerd');
for (const shared of ['@cloudflare/config', '@cloudflare/build-output-utils']) {
assert.equal(manifest(shared, tool), manifest(shared, voidEntry), name + ' installs a second ' + shared);
}
}
const manifestPath = findPackageJSON('@void/platform', voidEntry);
const entry = JSON.parse(readFileSync(manifestPath, 'utf8')).exports['./installer'].import;
Expand Down
2 changes: 1 addition & 1 deletion AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ Full-stack framework for Cloudflare Workers, powered by Vite.
- Documentation source lives in `docs/`.
- Docs is a Vitepress project using our custom theme. When asked to "link the theme", temporarily edit `docs/package.json` so that `@voidzero-dev/vitepress-theme` point to `link:../../../theme`. Rerun `vp install` to link it. Revert these when asked to "unlink the theme".
- Packages publish to npm as `void` and `@void/*`. Consumer-facing code, docs examples, playground source, and package manifests should use only those public package names.
- Published external runtime dependencies use compatible semver ranges. Pin `cf`, `@cloudflare/vite-plugin`, and `miniflare` as an exception: update them together so fresh installs share one Miniflare and workerd. Preserve `workspace:*` for dependencies and peers between Void packages. The lockfile fixes the versions tested in this repository. Keep the Sandbox SDK version aligned with its packaged Docker helper and verified platform helper layer.
- Published external runtime dependencies use compatible semver ranges. Pin `cf`, `@cloudflare/vite-plugin`, `miniflare`, `@cloudflare/config`, and `@cloudflare/build-output-utils` as an exception: update them together so fresh installs share one Miniflare and workerd. Pin `@cloudflare/config` and `@cloudflare/build-output-utils` to the exact versions `cf` and the Vite plugin depend on, so fresh installs share one copy of each. Preserve `workspace:*` for dependencies and peers between Void packages. The lockfile fixes the versions tested in this repository. Keep the Sandbox SDK version aligned with its packaged Docker helper and verified platform helper layer.

## Important Note for Release Workflows

Expand Down
2 changes: 2 additions & 0 deletions docs/guide/ai.md
Original file line number Diff line number Diff line change
Expand Up @@ -167,6 +167,8 @@ const response = await ai.provider('openai').fetch('/chat/completions', {
});
```

If the signal aborts while you read a streaming response, reading it rejects with the signal's reason instead of ending with a `void:error` event.

### OpenAI

```ts
Expand Down
2 changes: 1 addition & 1 deletion docs/guide/database/d1.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@ export default defineConfig({
});
```

If you self-host the Void platform, upgrade it as well before deploying. Upgrading alone or omitting the option does **not** disable existing replication.
If you self-host the Void platform, upgrade it as well before deploying. When the platform cannot apply `database.readReplication`, `void deploy` stops with an error before uploading anything. Upgrading alone or omitting the option does **not** disable existing replication.
:::

[D1 read replication](https://developers.cloudflare.com/d1/best-practices/read-replication/) is opt-in. Enable it in `void.config.ts`, then run `void deploy`:
Expand Down
8 changes: 4 additions & 4 deletions docs/guide/email/domains.md
Original file line number Diff line number Diff line change
Expand Up @@ -83,13 +83,13 @@ Setup enables the zone's plus addressing so `support+T-42@mail.acme.com` reaches

### Sending {#sending}

On Workers Free, `sendEmail()` can send to verified destinations listed under **Email Routing → Destination addresses** in Cloudflare.
On Workers Free, apps with `email/` handlers can send to verified destinations listed under **Email Routing → Destination addresses** in Cloudflare. Apps without `email/` handlers send through Email Sending, which requires [Workers Paid](https://dash.cloudflare.com/?to=/:account/workers/plans).

Configure your sender domain's SPF, DKIM, and DMARC records using [Cloudflare's email authentication guidance](https://developers.cloudflare.com/email-service/concepts/email-authentication/), then check the authentication results in a received message's original headers. A successful `sendEmail()` result confirms provider acceptance; it does not confirm delivery or authentication readiness.

Sending to arbitrary recipients requires [Workers Paid](https://dash.cloudflare.com/?to=/:account/workers/plans) and Email Sending onboarding. After upgrading, run `void email setup --platform cloudflare`. Void doesn't retry onboarding during ordinary deploys.
Sending to arbitrary recipients requires [Workers Paid](https://dash.cloudflare.com/?to=/:account/workers/plans) and Email Sending onboarding. After upgrading, run `void email setup --platform cloudflare`. Once setup is saved, deploys don't retry onboarding.

Existing DMARC or bounce-domain records can block onboarding; the checklist identifies conflicts to resolve. Inbound mail remains available.
Existing DMARC or bounce-domain records can block onboarding; the checklist identifies conflicts to resolve. Apps with `email/` handlers keep inbound mail.

The `void email usage`, `logs`, `destinations`, `allow`, and `disallow` commands apply to Void platforms.

Expand Down Expand Up @@ -118,4 +118,4 @@ Commit `void.lock.json`, then deploy in CI with:
void deploy --platform cloudflare --require-email
```

CI cannot answer setup prompts. Without `--require-email`, an unconfigured app can deploy without email. If setup is saved but DNS hasn't propagated, deployment waits for a later retry. For apps with inbound handlers, Workers Free setup for verified recipients satisfies `--require-email`. Sending-only apps must have an onboarded sending domain and a configured send binding.
CI cannot answer setup prompts. Without `--require-email`, an unconfigured app can deploy without email. If setup is saved but DNS hasn't propagated, deployment waits for a later retry. For apps with inbound handlers, Workers Free setup for verified recipients satisfies `--require-email`. Sending-only apps need an onboarded sending domain (Workers Paid) and a configured send binding.
4 changes: 2 additions & 2 deletions docs/integrations/cloudflare.md
Original file line number Diff line number Diff line change
Expand Up @@ -143,7 +143,7 @@ Set these CI secrets and variables as needed:
| `CF_ACCESS_CLIENT_ID`, `CF_ACCESS_CLIENT_SECRET` | When Cloudflare Access protects the readiness URL. |
| `CF_ACCESS_READINESS_ORIGIN` | When Access protects a route or Custom Domain and `workers_dev` is `false`. See [Cloudflare Access](#cloudflare-access). |

For email, run `void email setup --platform cloudflare` locally, commit `void.lock.json`, and pass `--require-email` in CI. The token also needs Email Routing Edit and Email Sending Edit.
For email, run `void email setup --platform cloudflare` locally, commit `void.lock.json`, and pass `--require-email` in CI. The token also needs Zone Read and Email Sending Edit, plus Email Routing Edit for apps with `email/` handlers.

#### Cloudflare Access

Expand Down Expand Up @@ -208,7 +208,7 @@ Void deploys native apps, static sites, SPAs, supported SSGs, and Cloudflare bui
- `--skip-build` works for existing static output. Worker apps require a fresh build.
- Named Cloudflare environments aren't supported. Use a separate Void project config for each target.
- Sandbox requires Workers Paid and Docker. See [Sandbox requirements](../guide/sandboxes.md#deployment) for plan and token permissions.
- Email to arbitrary recipients requires Workers Paid; verified recipients and inbound mail work on Workers Free. See [Email](../guide/email/domains.md#your-own-cloudflare-account).
- Email to arbitrary recipients, and all sending from apps without `email/` handlers, requires Workers Paid. Apps with handlers keep inbound mail and verified recipients on Workers Free. See [Email](../guide/email/domains.md#your-own-cloudflare-account).
- Node.js, Bun, and Deno use their [own deployment path](./nodejs-bun-deno.md).

Commit Durable Object migration history in `void.lock.json`. Do not delete or reorder deployed steps.
Expand Down
7 changes: 4 additions & 3 deletions docs/reference/cli/database.md
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,8 @@ Programmatic seed modules must export either a default function or a named `seed
```
void db execute <sql>
void db execute --file <path>
void db execute --remote <sql>
void db execute --remote <sql> [--yes]
void db execute --remote --file <path> [--yes]
```

Run ad-hoc SQL against the database. Provide SQL inline or from a file. A statement that returns rows prints them as a formatted table, and statements that change data print nothing. SQL with several statements runs as a script without printed results.
Expand All @@ -64,9 +65,9 @@ By default, targets the local database. Pass `--remote` to run against the deplo
- **Hosted PostgreSQL and MySQL projects**: fetches the stored connection string from the platform and connects directly.
- **Direct Cloudflare PostgreSQL and MySQL projects**: uses `DATABASE_URL` from the current shell; Cloudflare cannot return the password from Hyperdrive.

On direct Cloudflare D1 deployments, `--file` uses bulk import. Void waits for the import to finish and reports failures; bulk imports do not return individual query rows. Pass SQL inline to return query rows.
On direct Cloudflare D1 deployments, a `--file` larger than 100 KB runs as a D1 import: Void waits for it to finish, the database cannot serve queries until then, and query rows are not printed. Smaller files print rows like inline SQL.

For destructive statements (`DELETE`, `UPDATE`, `DROP`, etc.) when running in a TTY, you will be prompted to confirm before the query is sent to the deployed database. Non-TTY environments (CI) skip the prompt.
For destructive statements (`DELETE`, `UPDATE`, `DROP`, etc.) when running in a TTY, you will be prompted to confirm before the query is sent to the deployed database. A TTY also asks before a D1 import, whatever the file contains. Pass `--yes` to skip the prompt. Non-TTY environments (CI) never prompt, so `--yes` is optional there.

## `void db migrate` {#void-db-migrate}

Expand Down
2 changes: 1 addition & 1 deletion docs/reference/cli/email.md
Original file line number Diff line number Diff line change
Expand Up @@ -142,4 +142,4 @@ Set up email before deploying from CI. Requires `email.from` in `void.config.ts`

Void shows the planned changes and asks before applying them. Apps without `email/` handlers configure sending only; routing and plus addressing are left alone. Commit `void.lock.json`, then run `void deploy --platform cloudflare --require-email` in CI.

On Workers Free, inbound mail and sends to verified recipients remain available. Run this command again after upgrading to Workers Paid to enable arbitrary recipients. See [Email setup](../../guide/email/domains.md#your-own-cloudflare-account).
On Workers Free, apps with `email/` handlers keep inbound mail and sends to verified recipients. Sending-only apps need Email Sending, which requires Workers Paid. Run this command again after upgrading to Workers Paid to enable arbitrary recipients. See [Email setup](../../guide/email/domains.md#your-own-cloudflare-account).
Loading
Loading