Conversation
Contributor
Docker image |
Contributor
Docker image |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Highlights
The session and key model changed, so all users must log in again one time after this deploys. This is expected and one-time. DM history is preserved (the underlying private key is unchanged).
What's included
Max-Age+Secure+SameSite), with server-side session expiry, sliding refresh, a MongoDB TTL index, and crypto-strong unique tokens.CryptoKeyin IndexedDB. The server no longer issues thekeycookie.kdfmarker +deno task auth:statusto confirm migration.workflow_dispatch, fixing thestartup_failurethat broke v3.5.1's automated release.Post-deploy notes
deno task auth:status(run inside thechatcontainer) should report all real accounts migrated; the transitionallegacyPasswordpath can then be removed in a follow-up.