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, please take a look at our documentation.
Monitoring: avoid using global instance of ConfigFlags
Avoid using global instance of ConfigFlags in core monitoring code. This requires changes to GenericMonitoringTool. Currently the change is backwards compatible. If flags are not passed the global instance is taken.