Long-running sessions stop making redundant auto-update checks; there is no flag for it.
What's wrong with this entry?
An auto-update check is now skipped if one ran recently, so a long-lived session stops making redundant checks. The skip is logged with how many seconds ago the last check ran. There is no flag.
- Updater state (time of the last auto-update check, an update-restore failure marker, and minted preserved inodes) moved from module-level globals into one per-process object.
- The self-heal paths that restore a missing
claudebinary from a preserved<exe>.old.<timestamp>copy now receive that state explicitly instead of reading globals. - The npm install and uninstall shell-outs now resolve the home directory through a helper rather than calling
os.homedir()directly.
auto-update check throttled (last check
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.221
Four dead-code probes deleted along with the legacy paths they measured
Both mention updater