davidburstrom

After investigating this and https://junit.org/junit5/docs/5.9.1/release-notes/ I've found that one way to fix this is to release a new version of the pitest-junit5-plugin where the `junit.platform.version` is bumped to 1.9.1, so...

I'm creating a PR as we speak :)

> I'll try and take a proper look at this tomorrow. On the face of it the platform should be at provided scope so this sort of issue wouldn't happen....

Agreed, I just had a look at this in conjunction with the existing ConstantPatternCompile.