Stored credentials could survive a token change, but not in this build.
tengu_still_kestrel falls back to false.
tengu_still_kestrel Gate removed from the codeThis release deleted the gate from the code while it was still reading on for the account this site reads, so the code path no longer asks a flag before running.
This account: on · anonymous baseline: on · compiled default in v2.1.248: not a boolean we can read
Read once, for one account on one subscription tier, against v2.1.248. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
A new option decides whether stored credentials are kept when the token they belong to changes. It is controlled by the server-side gate tengu_still_kestrel, and with no server value the compiled fallback is false, so credentials are not kept in this build.
- The result is computed once and cached on the config object as
keepAcrossTokenChanges. - If the gate reader returns nothing at all, the helper also returns false.
keepAcrossTokenChanges
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