{"version":"2.1.232","anchor":"gitlab-tokens-and-the-glab-config-file-treated-as-secrets","canonical_anchor":"gitlab-tokens-and-the-glab-config-file-treated-as-secrets","heading":"GitLab tokens and the glab config file treated as secrets","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/gitlab-tokens-and-the-glab-config-file-treated-as-secrets","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### GitLab tokens and the glab config file treated as secrets\n\nMore GitLab token formats get redacted, and the glab config file is flagged as sensitive.\n\n**What**\n\nSecret redaction now catches more GitLab personal access token shapes, and the GitLab CLI config file joins GitHub's `hosts.yml` in the list of sensitive paths that command safety checks flag.\n\n**Details**\n\n- The token pattern now allows `=` in the body and an optional nine-character dotted suffix: `[A-Za-z0-9_=-]{20,}(?:\\.[0-9a-z]{9})?`.\n- The sensitive-path pattern now also matches `.config\/glab-cli\/config.yml`, alongside `.config\/gh\/hosts.yml`.\n\n**Evidence**\n\n`\\.config\\\/glab-cli\\\/config\\.yml\\b`\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}