DISABLE_AUTOUPDATER=0 or false no longer disables updates; only truthy values count now.
What's wrong with this entry?
Auto-update suppression used to fire on any non-empty value. It now goes through the shared truthiness parser, which accepts only 1, true, yes or on (case-insensitive, trimmed), so DISABLE_AUTOUPDATER=0 or =false no longer disables the updater as it did in 2.1.247. DISABLE_UPDATES is unchanged.
- The new check reads the process environment directly rather than the merged environment accessor, so whether a
DISABLE_AUTOUPDATERset inside a settings fileenvblock still takes effect depends on that path, which this code does not settle.
DISABLE_AUTOUPDATER
Strings lifted out of the shipped bundle, so the claim above can be checked against them.