Skip to content

Changelog

Every release, newest first. Each one is also a GitHub release, and the Upgrading notes say what to do when you deploy it. The JavaScript SDK hasits own changelog.

Unreleased (on main, not yet in a release)

Added

  • The JavaScript SDK, gentlemail on npm: send, read, reply and verify webhooks, typed, on Workers, Node, Deno and Bun. It has its own versions (packages/sdk/CHANGELOG.md) and a docs page. The webhook docs now describe the ping test event. (#17)
  • A Before you start section at the top of the deploy guide: what you need (a domain on Cloudflare, the Workers Paid plan, a GitHub account) and what it costs. The deploy guide is now the one place that explains deploying; the website’s /deploy page leads there. (#22)
  • The docs header shows the “gentlemail.” wordmark with a “docs” label, as on the social card, instead of the “g.” icon and typed title. (#24)
  • The docs have a social card (shown when a docs link is shared), a footer like the website’s with links back to it, and on phones a menu that unrolls from the header with its groups arriving one after another, like the website’s. (#23)
  • An SDK changelog page in the docs, and every section of the SDK page says which SDK version added it. (#20)

0.5.0 (2026-11-16)

Added

  • Documentation at gentlemail.dev/docs, with search: deploying, updating (including database migrations), two-step verification, spam, the API (keys, sending, reading, errors), webhooks and recipes, and this changelog. It lives in the repository (apps/docs), so docs change in the same pull request as the code. (#13)

Changed

  • The docs use Google Sans, like gentlemail.dev. (#14)

0.4.0 (2026-11-16)

Added

  • Two-step verification with any authenticator app: set up from Security (the menu under your name) with a QR code, 10 single-use recovery codes to download or copy, new codes on demand, and turning it off with a code. Signing in asks for the code after the password; 5 wrong codes and the password is needed again, and a code can’t be reused. (#10)
  • Admins can require two-step verification for everyone (people without it can only open Security until it’s set up), see who has it on, and reset it for someone who lost their phone. (#10)
  • Admins see the running version at the bottom of the sidebar, linked to the changelog. A build with changes not yet released shows +dev after the last release number (0.3.0+dev). Each release is tagged vX.Y.Z on GitHub with its changelog section as release notes. (#9)

Upgrading

  • Migration 0006_mfa.sql adds the two-step columns and tables. Nothing changes for anyone until they turn it on or an admin requires it.

0.3.0 (2026-11-16)

Added

  • This changelog, and AGENTS.md with the rules for changing the repository: every pull request adds its changelog lines. (#8)
  • API keys get Read and/or Send on all mailboxes, on a whole domain (mailboxes added to it later included) or on the mailboxes you pick, and Edit access changes an existing key’s access without replacing the key. GET /api/v1/mailboxes returns the key’s permissions on each mailbox. (#6)
  • README: tech stack, database and migration commands (plain SQL, no ORM), monorepo layout, every script, and an explicit note that no Cloudflare API token or account ID is ever needed. (#5)

Changed

  • Replying through the API with reply_to_message_id needs Read on the mailbox as well as Send, since the reply quotes and threads the original. (#6)
  • Opening a conversation marks it read through a server action once it’s on screen, instead of while the page loads. (#7)

Fixed

  • Conversations of more than 100 messages open again, and bulk actions (archive, trash, mark read…) work on selections holding more than 100 messages. (#7)
  • An incoming reply with a very long References header (a long email chain) is stored instead of failing. (#7)
  • Command-line deploy instructions: the first deploy creates the database before migrations run, and deploy needs a build first. (#5)

Upgrading

  • Migration 0005_api_key_grants.sql runs on deploy. Existing keys keep exactly the access they had (one mailbox or all mailboxes, with their read/send scopes). Keys with no known scope get no access.

0.2.0 (2026-11-16)

Added

  • “Not found” and “Access restricted” pages with the right HTTP status (404 / 403): for an unknown page, mailbox, conversation, domain or webhook, and for a mailbox or admin page you aren’t allowed to open. They show inside the app, with a way to sign in as someone else. (#4)

Fixed

  • Deleting a mailbox returns to the mailbox list instead of showing “Not found”. (#4)
  • Confirm buttons such as “Delete forever” use the destructive colour, and their text stays readable on hover. (#4)

0.1.0 (2026-11-13)

First public release.

Added

  • Multi-domain webmail on Cloudflare Workers: domains, mailboxes and users managed in Admin, with each person given access to the mailboxes they need.
  • Receiving through Email Routing, storage in D1 and R2, sending with Cloudflare Email Service. Conversations, search, attachments, signatures, sender name per mailbox.
  • Spam folder with rules, per-mailbox allowed and blocked senders, learning from “Spam” / “Not spam”, and a 30-day purge.
  • REST API with API keys, and signed webhooks (message.received, message.sent) with retries. (#1)
  • Sanitised HTML mail display with remote images blocked by default, theme-aware mail bodies.
  • Deploy to Cloudflare button, /setup with a one-time SETUP_TOKEN, MIT license. (#2)
  • The Worker name comes from wrangler.jsonc, and a complete deploy guide covers setup, domains, testing, configuration, updating and troubleshooting. (#3)