v1.3.1

Keyper v1.3.1

A patch release for 1.3.0.

Unlocking is fixed across runtimes. Keyper derives your key with Argon2id or PBKDF2 depending on what the runtime can load, and unlocking was picking based on the current runtime instead of the algorithm recorded with your vault key. The two produce different keys from the same passphrase, so a vault made in the desktop app could look like it had the wrong passphrase in the browser, and the other way round. Unlocking now honors what is stored.

The Supabase connection test works again. It was querying a protected table anonymously, which the 1.3.0 database rules correctly refuse, so a good configuration failed the test. It checks the Auth service now, and connection errors tell you which of the four likely problems you have.

Disconnecting your database is back in Settings. The Database tab shows your provider and endpoint with a Disconnect & reconfigure button, so switching between Supabase, Neon and SQLite no longer means clearing browser storage by hand. It deletes nothing: reconnect with the same passphrase and everything is there.

The Reset Options tab is now called Passphrase, and it no longer offers to change your master passphrase directly above a warning that it cannot be reset. Both statements were true, they were just filed under the wrong heading. No database migration. If you are on 1.3.0, just update. Coming from 1.2.x, do the 1.3.0 upgrade first.