Skip to content

Update to the latest Keyring and give sessions their user type - #19

Merged
entity merged 1 commit into
mainfrom
fix/keyring-session-user-type
Nov 11, 2026
Merged

entity merged 1 commit into
mainfrom
fix/keyring-session-user-type

Conversation

@entity

@entity entity commented Nov 11, 2026

Copy link
Copy Markdown
Owner

Bumps the lock to Keyring 639d305 (entity/keyring#88).

Keyring's session records now say which table their user's ID is one of, so this adds a migration for the new user_type column and its index. The app has one user model, so existing sessions are filled in rather than emptied and nobody has to sign in again. The same migration remakes the hash a reserved address is found by, since that folds "ß" and a doubled "s" together now.

Nothing else needed changing: the app takes the new 500ms timebox from the package's default.

Tested locally: 109 PHP tests, and the 35 browser tests on both PHP's own server and Octane.

@entity
entity merged commit 8c7bc64 into main Nov 11, 2026
@entity
entity deleted the fix/keyring-session-user-type branch November 11, 2026 20:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant