{"version":"2.1.248","anchor":"disable-autoupdater-now-needs-a-real-truthy-value","canonical_anchor":"disable-autoupdater-now-needs-a-real-truthy-value","heading":"DISABLE_AUTOUPDATER now needs a real truthy value","tier":"use","area":"Auto Updater","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/disable-autoupdater-now-needs-a-real-truthy-value","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### `DISABLE_AUTOUPDATER` now needs a real truthy value\n\nDISABLE_AUTOUPDATER=0 or false no longer disables updates; only truthy values count now.\n\n**What**\n\nAuto-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.\n\n**Details**\n\n- The new check reads the process environment directly rather than the merged environment accessor, so whether a `DISABLE_AUTOUPDATER` set inside a settings file `env` block still takes effect depends on that path, which this code does not settle.\n\n**Evidence**\n\n`DISABLE_AUTOUPDATER`\n\n- Area: Auto Updater\n- Names: `DISABLE_AUTOUPDATER`, `DISABLE_UPDATES`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5"}