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 ·

Nine more GitLab token types are caught by the secret scanner

Nine more GitLab token types are now caught and masked by the secret scanner.

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
1Signal: worth watching, 1 to 5
Secret RedactionArea: what it touches
ImprovementsKind: in v2.1.232,
ImprovementsSection of the release
What

The scanner replaced its two hard-coded GitLab patterns with a shared, looser suffix match and added nine prefixes, all at high confidence: runner authentication (glrt-), OAuth app secret (gloas-), pipeline trigger (glptt-), Kubernetes agent (glagent-), incoming mail (glimt-), SCIM OAuth (glsoat-), CI build (glcbt-), feed (glft-) and feature-flag client (glffct-).

Details
  • The shared suffix is [\w=-]{20,}(?:\.[0-9a-z]{9})?, which is broader than the previous fixed 20-character match, so longer and dotted token forms are now caught too.
Evidence

gitlab-feature-flag-client-token

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 secret redaction for GitLab token families (glrt-, gloas-, glptt-, glagent-, glimt-, glsoat-, glcbt-, glft-, glffct-) and full…

See this entry in the whole of v2.1.232 →

Feedback