Token refresh, logout, onboarding reset and plugin loading now take a storage handle rather than global state.
What's wrong with this entry?
checkAndRefreshOAuthTokenIfNeeded now receives a v5 storage handle alongside credentials, and the same pair travels through hook execution, session-team registration, logout and onboarding reset, plugin loading and the file-history writers. Login state can therefore live in that store rather than in process-wide state.
checkAndRefreshOAuthTokenIfNeeded
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Signing back into the same account keeps a pending auto-resume
Both mention auth
-
v2.1.234
Token screen reports actual remaining validity
Both mention auth
-
v2.1.234
Setup-token login result carries the expiry
Both mention auth