Expired logins during code sessions now refresh and retry automatically instead of failing the operation.
What's wrong with this entry?
HTTP failures from code-session calls are classified in one place, and a 401 is treated as recoverable so the caller refreshes OAuth and retries instead of failing the operation.
- one helper returns
"oauth_rejected"for 401,"transient"for 408, 429 and any status >= 500, and"rejected"otherwise - 401 yields
{ terminal: !1, reason: "oauth_rejected" } - the type guards now check
e.terminal === !0/e.terminal === !1rather than testing for the presence of aterminalkey - the bridge's 401 retry path also fires when the result is any non-terminal failure
oauth_rejected
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