# Updating to v0.26.0

For users already on v0.25.x, install the new version with your existing settings and run a normal sync. Kei updates its saved state automatically, even when you open it with `kei status`, so make the backup below first.

If you're on v0.24.x or earlier, follow the [older-version instructions below](#updating-from-v024x-or-earlier) before starting the new version.

## Update and sync

1. Stop kei and any scheduled syncs or automatic updates. Stop other programs writing to the same photo folders while you make the backup.
2. Back up your complete kei setup and photo folders together: configuration, saved state, photos, videos and accompanying metadata files. Copy the whole state directory, including any database files ending in `-wal`, `-shm` or `-journal`. Keep this backup separate and unchanged, check that it copied successfully, and retain the old binary or container image.
3. Install [v0.26.0](https://github.com/rhoopr/kei/releases/tag/v0.26.0). Keep the same account, iCloud region, directories, library and album choices, and metadata settings. Start with one kei process.
4. Run your usual sync command. Read the final summary for unfinished work or errors; downloaded files alone don't mean the whole backup is complete. If files change unexpectedly or kei cannot save its state, stop and report it.
5. Report any problem that remains or comes back. Include the version, what happened, and the normal run output after checking it for private information. You can also use [support export](support-export.md) to collect saved details without another sync. Review the export before sharing it.

You don't need a special diagnostic build or debug flags. Keep kei's state between runs. Don't reset it, delete saved records or prune files to force an incomplete sync to finish.

## Updating from v0.24.x or earlier

These versions need a separate step to confirm which account owns the existing state. Follow [Back up and adopt existing state](v0.25-upgrade.md#back-up-and-adopt-existing-state), including its login instructions. Don't guess ownership or rename old authentication files to make them fit.

## What to expect

More recovery work can happen during normal sync, but some files may still wait for reliable information from iCloud. Kei won't guess which file or account owns an item. Accepting an older local file doesn't prove its identity in iCloud. Work can remain incomplete while kei is still checking a library or when you've selected only part of it.

Kei combines supported duplicate saved responses that differ only in refreshed download links. This can free space within its storage allowance without making the database file smaller on disk. Different or unrecognized responses still use space, so storage limits can still be reached. Don't delete saved information to bypass a limit.

Existing duplicate files and previously damaged media aren't repaired automatically. Keep your metadata settings unchanged during the update; see the [metadata guidance](metadata.md) for what those settings can change.

## Going back to an older version

Replacing the binary alone is not enough: older versions cannot read the updated state.

Stop kei and other programs writing to these folders. Save a separate copy of the current setup, then restore the complete backup made before the update: configuration, the entire state directory, photo and video folders, and accompanying metadata files. Use the old binary or container image with that restored set.

Don't restore only the database, combine files from different backups, or edit the database's version number.