Kaeso 0.3.2. Released 21 October 2026, with 8 changes.

GET me/sign-in-again lists how the signed-in account can confirm a recent sign-in, narrowed to an organization's own single sign-on when org requires it, and whether it can set a password by email first. POST me/sign-in-again/sso starts a confirmation at a linked organization's identity provider.

Confirming a recent sign-in through single sign-on no longer loops. The console opens the identity provider in a window of its own, the page and what you typed stay, and the action repeats by itself once you've signed in there; a refusal says why instead of asking again.

Add models says when a model's values can't load instead of staying silent.

An account without a password, such as one that signs in through single sign-on, gets a link by email to set one: from Email me a link under Account › Security, and in the dialog when an action needs another sign-in and nothing else works. Both used to end at a step it couldn't take.

A sign-in ends the session its browser had, so signing in again to confirm an action no longer leaves a session behind each time; Sessions listed dozens for one browser.

Valkey starts again on an install that already has data. Since 0.3.0 its container started as root without capabilities, so it couldn't enter its own appendonlydir and exited, which rolled back an upgrade from 0.2. It now runs as the image's own user and needs no capabilities.

The updater verifies releases again. It asked GitHub for a release's attestations at an address that read sha256:… as a URL of its own, so every update from the console or in a window was refused with "cannot be fetched (request failed)". Installs that use the updater update to this release by hand once; from then on it updates them itself.