Repository navigation
fix: update UMPK to 0.9.0-beta.6 and preserve cached logins - #4
Merged
Merged
Conversation
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.
Updates all nine UMPK pins to
0.9.0-beta.6and refreshes the current dependency guides.Enabled memory caches now retain login tokens across reconnects within one client. Disabled caching still starts each attempt empty. Modern profile signing checks
Session.IsAuthenticated, so encrypted offline sessions do not announce certificates for the account's online UUID. The public constructor parameter name stays compatible.Validation:
The authentication regressions use cached fake credentials and a scripted encrypted server.