{"version":"2.1.286","anchor":"runner-child-env-spread-gets-a-constant-false-slot","canonical_anchor":"runner-child-env-spread-gets-a-constant-false-slot","heading":"No-effect change to the environment given to self-hosted runner processes","tier":"internal","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/runner-child-env-spread-gets-a-constant-false-slot","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### No-effect change to the environment given to self-hosted runner processes\n\nThe environment a self-hosted runner gives the processes it starts gained an empty entry that adds nothing\n\n**Unclear.** What this entry originally was is not known, and it may simply be a build leftover.\n\n**What**\n\nThe environment that a self-hosted runner hands to the processes it starts gained an entry that adds no settings, so nothing changes in practice.\n\n**Why**\n\nIt likely marks something removed from this part of the code when the build was made.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}