Saved login tokens now propagate into the newer storage-backed credential cache.
What's wrong with this entry?
After either token-save path writes, it now clears the in-process caches and waits for the new value to propagate into the version 5 storage handle when that handle exists, passing along whatever was cached before.
- A related helper was cut down to a cache reset plus a conditional refresh.
- Only the storage version 5 path does the propagation step.
tengu_oauth_tokens_saved
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