Skip to content

Releases

0.5.0

Choose a tag to compare

@theophane05 theophane05 released this 16 Nov 20:49
c834a4d

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)

GentleMail 0.4.0

Choose a tag to compare

@theophane05 theophane05 released this 16 Nov 16:55
a99cb68

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.

Full history: CHANGELOG.md

GentleMail 0.3.0

Choose a tag to compare

@theophane05 theophane05 released this 16 Nov 16:53
8abeaae

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.

Full history: CHANGELOG.md