Login credentials are now handed to each auth and API path instead of being read from one shared spot.
What's wrong with this entry?
Auth and API call paths now receive credentials as an argument rather than reaching for one process-wide set: OAuth refresh, first-party API startup load, quota checks, web fetch and remote environment listing all take and forward them, and the signed-out check became asynchronous and takes the credential object. This is groundwork for a session carrying its own credentials.
- A helper installs credentials on the API client and disposes and resets it when they go away.
await ov({ credentials: e });
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