GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.
This should avoid ambiguities between regexes, in case more are added in the future.
Furthermore, this also gives nice notice when one forgot to add the radius index for bamps output,
as implemented in !5.