Very old config files with legacy updater values now migrate to an unknown install method.
What's wrong with this entry?
The probes that measured whether legacy shapes were still reached are gone, and so are the fallbacks they covered.
- env_manager_log no longer accepts a flat
messagefield - the global-config env probe is removed
- the background attach probe is removed; the no-control-key path still logs a warning and is still allowed
- config migration no longer maps autoUpdaterStatus "installed", "no_permissions" or "not_configured" onto install methods, so very old configs with those values now migrate to an unknown install method
tengu_dead_probe_autoupdater_status
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.242
Binary updates can download a zstd-compressed build
Both mention updater
-
v2.1.242
Update manifest fetches retry when the connection drops
Both mention updater
-
v2.1.242
Auto-update checks are throttled within a long-running process
Both mention updater