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.
CA-based campaign config should have separate functions for pile-up and non-pile-up cases
CA-based campaign config should have separate functions for pile-up and non-pile-up cases. In this case we do not need to depend on the digi pile-up flag, which is not set downstream.