HotLoop Cascade 1.0.1 release notes

What this is

1.0.1 fixes one mistake in how sign-in treats a database that can’t be read. Nothing else changed from 1.0.0.

The fix

When the database blinked, Cascade read “I couldn’t look that up” as “that isn’t valid”, and answered 401. A session check, an API key, a SCIM token and a key’s user all did it, and the session check also cleared the cookie, so a short outage signed everyone out. Now only a session that doesn’t exist or belongs to a disabled user is a 401. A store that can’t be read answers 503 with a Retry-After, and the cookie stays.

The second factor had the same problem. During an outage, a good authenticator code, recovery code or passkey was answered as a wrong code, which can lock a person out of their own account. Those steps answer 503 for a store or server error now and keep 401 only for a real refusal: a wrong code, a failed passkey, an expired request. Passkey sign-in also no longer reads a failing user lookup as “no account has that passkey”.

Tests for each of these fail on 1.0.0 and pass on 1.0.1.

Upgrading, and going back

No migrations. helm upgrade to 1.0.1, or let :stable roll the Quadlet units. Because nothing in the database changes, putting 1.0.0 back is safe. A backup before any update is still the right habit.