Adam

Hi @charleskorn, are you able to take a look? I'd like your thoughts since you recently refactored the plugins.

> Before I review this myself, is the version now required to be set ? > > ``` > kotest { > kotestCompilerVersion.set("5.4.2") > } > ``` > > Or...

@sksamuel No it's okay, this can be closed. I'll pick up the remaining bit of work (creating automated tests) in #3163 if/when I have time/motivation

@jbartok I made this commit through the GitHub web gui which doesn't have this option. My GitHub email and username are already in the commit, so it looks like it's...

Would you be able to add a test using the example that failed? (A sealed class with an abstract child?)

Yes the stacktrace helps, thanks, although I can't figure out exactly what's wrong. At least I think it shows that we're on the right path! I don't see any reference...

That is indeed weird! Good catch. I think the new Gradle GHA is re-using the cache for different JDK versions. I see this message in the logs: `Task :modules:mockk:test SKIPPED`

I thought that because there was an issue with the Gradle tests not failing https://github.com/mockk/mockk/pull/916#issuecomment-1240443435 that it wasn't clear if this PR would work as expected. I don't have any...

Let's do it then 👍

Can you include more of the stack trace? I can't see any reference to `io.mockk` so it's hard to see what part of MockK is going wrong.