Changelog and upgrade notes

Release notes are published with every release on GitHub. This page collects what to check when you upgrade.

Where releases are announced

GitHub releases: notes generated from the merged changes, the archives for every platform and checksums.txt. Tags look like v1.2.3; pre-releases like v1.3.0-rc.1 are marked as such.
ghcr.io/ja7ad/meilisearch-cdc: images tagged 1.2.3, 1.2 and, for final releases, latest.

Upgrade checklist

Read the notes of every release between your version and the target.
Back up the data directory and the key.
Replace the binary or the image tag, restart, and watch the tasks resume from their checkpoints.
Reload open dashboards (installed apps offer Reload by themselves).

Upgrade notes

Notes that need action from operators will be listed here, newest first.

No breaking changes recorded yet

Data written by older versions is migrated on start where needed. For example, an installation from before the primary administrator existed gets its oldest admin promoted to owner, and secrets stored in an older encryption format are re-encrypted with the current key.