Mnema Talk 1.0.0 releaseĀ notes

From mnema-talk v3.3.13, rendered on this site.

The generated list of changes is in CHANGELOG.md (release-please writes it from the commits). This page is what the changelog cannot say: what 1.0 promises, what it does not, and what to do before updating. The release pull request body can link here. This page describes 1.0; for the move to 1.1 read the 1.0.x to 1.1.0 notes.

What is new in 1.0

  • Chat: pinned messages, /poll and other slash commands, custom emoji per community, edit history, drafts per channel, jump to the first unread message, and Markdown with code highlighting.
  • Accounts: optional e-mail (with SMTP, also password reset), two-factor sign-in with recovery codes, self-service account export and deletion.
  • Installable web app with Web Push notifications, and a phone layout.
  • Rules and onboarding for new members.
  • Talks: sealed media on Chromium, Safari (WebKit) and Firefox; browsers that cannot seal media are refused at the join (see Browsers).
  • Roles, moderation (timeouts, bans), webhooks, bots and the audit log, as in 0.9, now under the stability promises below.

Stability promises

From 1.0.0 Mnema Talk follows semantic versioning for the surfaces in api-stability.md. Concretely, for every 1.x:

  • Your clients, bots, webhooks, dashboards and alerts keep working. The REST API (api/openapi.json), WebSocket event names and payloads, bot gateway and bot API, incoming and outgoing webhook formats, the desktop client contract and bridge, documented environment variables (names, meaning, defaults) and Prometheus metric names are only extended in a minor release, never changed incompatibly.
  • Breaking changes wait for 2.0. Anything on that list is deprecated in a minor release first (announced in the changelog and doc/api-stability.md) and removed no earlier than the next major version. CI fails an incompatible change to the OpenAPI document unless a commit carries a BREAKING CHANGE: footer.
  • Upgrades are forward-only and tested. Migrations run at startup and are never edited after release. CI installs each supported earlier release, seeds data through its own API, upgrades to the build under test and checks the data, then checks that a backup of the old release restores into the new one and that the old release refuses to start on migrated data. Rollback means restoring the backup taken before the update (upgrade.md).
  • Safe defaults stay safe. MEDIA_RETENTION_DAYS=0 (nothing deleted automatically), invite-only registration and a single Owner who nobody can restrict do not change in a minor release.
  • Security fixes ship as patch releases for the latest minor and, once a newer minor exists, the previous one for 90 days. 0.9.x and older get no fixes (SECURITY.md).

Not covered by the promises: the database schema, internal/... Go packages, operator-only admin endpoints, log text and UI wording (the full list). The desktop clients are Beta and unsigned (how to install them).

What 1.0 is not

  • Not an externally audited release. The internal security review found no Critical or High issue and fixed every Medium one; the items it deferred are listed there.
  • No end-to-end encryption of text: messages and attachments stay readable by the server. Voice, camera and screen payloads are sealed in the browser (product-status.md).
  • No signed or notarised desktop installers, and no capacity claim beyond the recorded load tests.

Before you update from 0.9.x

Read the 0.9.x to 1.0.0 notes, then follow the update procedure with a backup first. The short version:

  1. Ten migrations (0038 to 0048; 0046 is intentionally unused) run on first start; upgrade.md calls out the two that take longer (0044 and 0047).
  2. Weak custom invite codes stop working; regenerate them.
  3. Uploads are limited to 2 GiB per account and 24 hours by default (UPLOAD_QUOTA_MB_PER_DAY, 0 = off).
  4. coturn gets allocation quotas; fetch the compose file of the tag.
  5. An http:// PUBLIC_URL in production logs a warning.
  6. Regenerate bot tokens you still use so they are bound to their issuer.

New to Mnema Talk? deployment.md installs 1.0 from scratch, and operations.md has the metrics and the ready-made alert rules.

Something wrong on this page? Tell us.