v2.0.0
Latest
v2.0 — one shared worker, no address to configure
The platform's mail worker is one shared deployment reached through a service binding, so it has no address, no secret and nothing to configure. Its address is gone from every surface — and with it the gate that stopped a working deployment from issuing API keys.
Breaking changes
Heads up before you upgrade
- `GET /api/v1/me` no longer answers `workerHost` — one shared worker serves every tenant, so the address said nothing about the credential
- `GET /api/v1/worker-version` no longer answers `workerHost`, and its response carries `version` / `bootstrapped` / `lastDeployAt` / `lastDeployError`
- The SDK's `AccountInfo.workerHost` and `WorkerVersionInfo.workerHost` are gone — see `packages/sdk/CHANGELOG.md` for the migration
Highlights
What's new
- API keys are issued on any deployment — the worker address is no longer a prerequisite
- `GET /api/v1/worker-version` answers from the worker's own version probe instead of 404-ing when the deployment publishes no address
- A failed key creation leaves no key behind: the row is compensated, so a failed attempt no longer occupies a quota slot
- The SDK's KV credential record carries the scope only — the worker's address is no longer copied into it
Fixes
Bug fixes
- Creating an API key no longer fails with "the shared mail worker is not configured on this deployment"
- A key that could never authenticate no longer lingers in the dashboard after a failed creation
Other releases