{"version":"2.1.239","anchor":"global-config-keeps-its-file-permissions-defaulting-to-owner","canonical_anchor":"global-config-keeps-its-file-permissions-defaulting-to-owner","heading":"Global config keeps its file permissions, defaulting to owner-only","tier":"notice","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/global-config-keeps-its-file-permissions-defaulting-to-owner","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Global config keeps its file permissions, defaulting to owner-only\n\nYour global config file keeps its permissions, defaulting to owner-only instead of following umask.\n\n**What**\n\nRewrites of the global config file now read back and reuse the file's existing permission bits, falling back to 0600 (owner read\/write only) if they cannot be read. Previously the result depended on the process umask.\n\n**Evidence**\n\n`t.ok && t.value.mode !== void 0 ? t.value.mode : 384`\n\n- Area: Internals\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}