{"version":"2.1.232","anchor":"gitlab-cli-credentials-get-the-same-sandbox-protection-as-gi","canonical_anchor":"gitlab-cli-credentials-get-the-same-sandbox-protection-as-gi","heading":"GitLab CLI credentials get the same sandbox protection as GitHub CLI","tier":"notice","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/gitlab-cli-credentials-get-the-same-sandbox-protection-as-gi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### GitLab CLI credentials get the same sandbox protection as GitHub CLI\n\nSandboxed commands can no longer read your GitLab CLI credentials.\n\n**What**\n\nSandboxed commands are now blocked from reading GitLab CLI credentials the way GitHub CLI ones already were.\n\n**Details**\n\n- `.config\/glab-cli` is created and scrubbed in the home directory alongside `.config\/gh`, and `.git\/glab-cli` is removed by the git-scrub paths (four call sites).\n- The regex that flags a read as touching credentials now matches `.config\/glab-cli\/config.yml` next to `.config\/gh\/hosts.yml`.\n\n**Evidence**\n\n`glab-cli`, `.config\\\/glab-cli\\\/config\\.yml\\b`\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}