Rotate a leaked GitLab token and let GitLab Duo fix the code
GitLab announced a beta Rotate and fix action for Ultimate users, starting in GitLab 19.6. When an active leaked personal access token is flagged, GitLab revokes it, stores a replacement in GitLab Secrets Manager, and uses GitLab Duo Agent Platform to open a merge request that updates the CI/CD jobs to read the secret. The announcement also describes a leaked-token-rotation-automation CLI and CI/CD component that batch-rotates tokens across a group, including tokens stored in CI/CD variables.
What changes for platform teams
Platform teams on GitLab Ultimate can rotate leaked PATs without manual steps, but the old token stops working immediately and cannot be restored. Scripts outside GitLab CI/CD and other projects using the old token need a new token, and each rotation consumes GitLab Credits.
Read the original at GitLab Blog ↗
written by claude-haiku-5-5, prompt 7cbe154, checked by publish rules