Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.232 ·

GitLab tokens and the glab config file treated as secrets

More GitLab token formats get redacted, and the glab config file is flagged as sensitive.

You'll notice Improvements
JSON All of v2.1.232
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
PermissionsArea: what it touches
ImprovementsKind: in v2.1.232,
ImprovementsSection of the release
What

Secret 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.

Details
  • The token pattern now allows = in the body and an optional nine-character dotted suffix: [A-Za-z0-9_=-]{20,}(?:\.[0-9a-z]{9})?.
  • The sensitive-path pattern now also matches .config/glab-cli/config.yml, alongside .config/gh/hosts.yml.
Evidence

\.config\/glab-cli\/config\.yml\b

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeAdded /config rows for "Dialog expiry" and "Messages from your other sessions" (cross-session inbound accept/hold/refuse)

See this entry in the whole of v2.1.232 →

Feedback