A small one this time, and one you will not see.
When a new version of Rekindly starts for the first time, it brings the database up to date. Usually that means a new table or a new column. So far that has always gone smoothly, but "so far" is not a promise, and everything you have written down about the people in your life is in that one file.
From 0.3.1 on, Rekindly saves a copy of the database before an update changes anything. It goes to /data/backups, right next to the database, and the newest three are kept. If the copy cannot be written, for example because the disk is full, Rekindly leaves everything as it is, does not start, and says why in the log. It would rather wait than update without a way back.
Two more things happen quietly. While the database is being updated, a change to one table can no longer take rows in other tables with it. And afterwards Rekindly checks that every note, fact and link still points to the person it belongs to. If something does not add up, it stops and tells you where the copy is, instead of carrying on as if nothing had happened.
You do not need to do anything. 0.3.1 itself does not change the database, so the first copy appears with the next update that does. Your regular backups stay what they are: this is a safety net for the moment of an update, not a replacement for them.
More small updates will follow over the coming weeks. Some you will see, some you will not.