mindfork 0.23.1 — a backup says what it holds

mindfork 0.23.1 is out. It is a small release with one fix, for the way back to the version before.

The way back, without the false alarm

Before it upgrades your data, mindfork makes a backup of it as it was — backups/pre-migrate-….zip — so that the version before can take it back. Until now, that version restored the copy with a warning: this backup was created by a newer version of mindfork, and the current version may refuse to open the data. Then it read every chat in it. The warning was wrong, and it stood on the very copy made for going back.

A backup carries a small manifest that says which data formats it holds, and it used to record the formats of the version that wrote it. Every backup now records the formats of the files it actually packs, so:

• the backup made before an upgrade restores into the version before without a word;
• so does mindfork backup run by a new version before its first start, while the data is still in the old format;
• so does the copy restore makes of data that was restored but not yet opened.

When the warning is due — a backup that does hold data newer than the version restoring it — it now names the files and their format numbers, the same words the app uses when it refuses newer data at start.

A backup 0.23.0 already made still carries the old record, so 0.22.0 still warns on it. The warning is harmless: 0.22.0 reads every chat in that copy.

Your data

Nothing is migrated, and a backup's manifest keeps its shape — the same four format numbers. Checked with the published 0.23.0 and 0.22.0: 0.23.0 restores a backup this version made and starts on it, with the same chats; 0.22.0 restores the backup this version makes before upgrading 0.22.0's data with no warning and every chat in it.

The full list is in the changelog; downloads are on the releases page, and cargo install mindfork builds the same version from crates.io.