Changelog¶
2026-Q2 (Unreleased / Rolling)¶
- Two-factor authentication: Optional TOTP + 10 single-use recovery codes for all users; admin force-reset via
/admin/mfa. Shipped 2026-05-12. - Row-Level Security: Postgres RLS enforced at the database layer for projects, workspaces, integrations, and GitHub connections. Every tenant's data is isolated even if application-layer auth is bypassed. Live 2026-05-11.
- Provider Bridge: Platform-managed AI provider credentials. Workspace admins configure shared API keys once; members select a provider without ever seeing the raw key. Backend shipped; usage dashboards coming.
- Sandbox allowlists: Workspace-owned allow/deny rules for AI tool access and network egress. Schema, rule-matcher, and admin CRUD API shipped (migration 073); OS-level enforcement in progress.
- Personal vs workspace AI scope: Any workspace member can now add their own personal Copilot account or custom AI provider. Personal rows are invisible to other members and workspace admins. Migration 072.
- doable-cli TUI: Rust all-in-one operator binary (
doable install/doable admin [--remote]) with 9 sidebar screens covering users, feature flags, AI settings, credits, server config, and DB credential rotation. Shipped 2026-05-09. - DNS wildcard
/admin: Automated*.doable.mesubdomain provisioning with CF API token KEK-encrypted storage and systemd-based renewal; rounds 1-7 complete.
The authoritative changelog lives on GitHub:
- Releases: https://github.com/doable-me/doable/releases
- Commits: https://github.com/doable-me/doable/commits/main
For self-hosted operators, the release notes call out:
- Breaking changes (env var renames, schema changes, removed features).
- New required env vars.
- Migration steps beyond
pnpm db:migrate. - Security advisories with severity and recommended action.
Subscribe to releases on the GitHub repo (Watch, Custom, Releases) to get an email whenever a new tag ships.
Versioning¶
Doable follows Semantic Versioning loosely:
- Major: breaking schema or API changes; read the release notes carefully.
- Minor: new features, backward compatible.
- Patch: bug fixes, dependency bumps.
Pre-1.0, expect occasional breaking changes in minor releases. They'll be called out in the notes.
Upgrade guide¶
See Upgrading for the per-deployment-mode upgrade procedure.