I'm currently working on implementing a new check, and while running the CI, I noticed that all Pitest checks are failing—even in areas where I haven't made any code changes.

Has there been any recent update or change to the Pitest CI configuration that might be causing this issue?

Interestingly, the same code passed all Pitest checks just four days ago. I also reviewed other recently opened PRs, and it seems they're experiencing the same problem-Pitest failures even when the code changes are unrelated.

Here’s a list of Pitest modules that I suspect may have been updated and could be causing the issue:
ant, coding, filters, header, imports, javadoc, packagenamesloader.