What changed in each version of Catch. Preview versions come out ahead of stable ones.
The same build as v0.6.3-preview, released as stable.
API protocol: app 3 → 5; server supports 2–3 → 2–5. Update the server before the apps: this app cannot sync with the previous server, while apps from the previous release keep working with this one. Local notes and queued writes are kept while sync is paused.
Breaking changes
- links: choose a link as the gallery preview
the new client requires protocol 5 for synced gallery preview choices. Update the server before clients; the server continues to support protocol 2–4 clients and their queued writes.
- sharing: share notes as Catch links or Markdown
clients use API protocol 4; servers support protocols 2–4. Update the server first. Existing protocol 2/3 clients, queued writes and their shapes are preserved. Migration 0014 backfills reader tokens and the shared-notes collection uses schemaVersion 2.
DownloadsEvery change
DownloadsEvery change
API protocol: app 4 → 5; server supports 2–4 → 2–5. Update the server before the apps: this app cannot sync with the previous server, while apps from the previous release keep working with this one. Local notes and queued writes are kept while sync is paused.
DownloadsEvery change
DownloadsEvery change
API protocol: app 3 → 4; server supports 2–3 → 2–4. Update the server before the apps: this app cannot sync with the previous server, while apps from the previous release keep working with this one. Local notes and queued writes are kept while sync is paused.
DownloadsEvery change
The same build as v0.5.1-preview, released as stable.
API protocol: app 2 → 3; server supports 2 → 2–3. Update the server before the apps: this app cannot sync with the previous server, while apps from the previous release keep working with this one. Local notes and queued writes are kept while sync is paused.
Breaking changes
- site: add the public site with a marketing page, docs skeleton and changelog
docker-compose.yml runs the published image instead of building the checkout. A server built from source must set COMPOSE_FILE=docker-compose.yml:docker-compose.build.yml in .env before updating (see DEPLOYMENT.md).
- reminders: add note reminders with Web Push and Android alarms
API protocol 3. Servers support protocols 2-3, so apps from the previous release keep syncing, without reminders. Update the server before the apps: a protocol 3 app pauses sync against an older server, keeping its notes and queued writes until the server is updated.
DownloadsEvery change
DownloadsEvery change
DownloadsEvery change
DownloadsEvery change
DownloadsEvery change
API protocol: app 2 → 3; server supports 2 → 2–3. Update the server before the apps: this app cannot sync with the previous server, while apps from the previous release keep working with this one. Local notes and queued writes are kept while sync is paused.
Breaking changes
- reminders: add note reminders with Web Push and Android alarms
API protocol 3. Servers support protocols 2-3, so apps from the previous release keep syncing, without reminders. Update the server before the apps: a protocol 3 app pauses sync against an older server, keeping its notes and queued writes until the server is updated.
DownloadsEvery change
The same build as v0.3.2-preview, released as stable.
Breaking changes
- tags: add nested tags and search filters
clients and servers now require API protocol 2. Upgrade the server before clients; queued writes and device notes retain their existing formats.
- security: harden exposed servers and add admin invites
sign-up is closed after the first account by default; set REGISTRATION=open to add accounts. The bare session token from a sign-in response body is no longer accepted as a bearer token; use the set-auth-token header value. Restoring a backup signs everyone out except the admin who started it.
- sync: enforce client/server protocol compatibility
Data APIs now require a supported X-Catch-Protocol header. Existing clients must update to protocol 1; new clients pause sync against unversioned servers.
DownloadsEvery change
DownloadsEvery change
DownloadsEvery change
API protocol: app 1 → 2; server supports 1 → 2. Update the server first, then every app: apps from the previous release cannot sync with this server, and this app cannot sync with the previous server. Local notes and queued writes are kept while sync is paused.
Breaking changes
- tags: add nested tags and search filters
clients and servers now require API protocol 2. Upgrade the server before clients; queued writes and device notes retain their existing formats.
- security: harden exposed servers and add admin invites
sign-up is closed after the first account by default; set REGISTRATION=open to add accounts. The bare session token from a sign-in response body is no longer accepted as a bearer token; use the set-auth-token header value. Restoring a backup signs everyone out except the admin who started it.
DownloadsEvery change
DownloadsEvery change
DownloadsEvery change
DownloadsEvery change
API protocol 1 is introduced; the server supports 1. The previous release has no compatibility check: sync or export pending changes, then update the server and every app together.
DownloadsEvery change
DownloadsEvery change
DownloadsEvery change
DownloadsEvery change