Procedure for testing/pinning new correctionlib versions

What should the procedure for handling new releases in correctionlib be within this area? I see the version is set in https://gitlab.cern.ch/cms-analysis-corrections/scripts/-/blob/master/tests/requirements.txt?ref_type=heads#L2 but the CI script runs in a container per https://gitlab.cern.ch/cms-analysis-corrections/scripts/-/blob/master/tests.yml?ref_type=heads#L8 and I'm not sure what the update schedule for that is.

I've just made a prerelease https://pypi.org/project/correctionlib/2.8.0rc1/ and want to make sure it doesn't break this CI. But perhaps all I should do is run the validation myself on all the json currently in cvmfs?