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.
The JetFitter configuration includes a strip hit requirement not adapted for the ITk geometry in the forward region. As for SV1, this requirement is relaxed when a Run4 configuration is run with this MR.