{"version":"2.1.271","anchor":"gh-repo-list-subprocess-call-no-longer-inherits-the-parent","canonical_anchor":"github-cli-calls-now-run-with-an-isolated-environment","heading":"Subprocess calls now run with an isolated environment via extendEnv","tier":"notice","area":"Git","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/gh-repo-list-subprocess-call-no-longer-inherits-the-parent","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Subprocess calls now run with an isolated environment via extendEnv\n\ngh CLI and other subprocess calls now run with an explicit environment instead of inheriting the full parent process environment\n\n**What**\n\n- Calls to the `gh` CLI (for GH_TOKEN lookup and repo content fetches, and for `gh repo list` during auto-mode sibling-repo lookups) now build their environment from an explicit snapshot with `extendEnv: false`, instead of spreading the entire `process.env` into the subprocess.\n\n- An `extendEnv` option was plumbed more generally into the shared exec-options builder and into other spawn call sites.\n\n**Why**\n\nThis stops `gh` and other spawned subprocesses from inheriting the parent process's full environment, reducing the chance of leaking unrelated environment variables into these subprocess calls.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}