Adam

That's a good point @sksamuel. I have also been thinking about property based tests, which has a separate listener system. It would be nice to unify the before/after checks, so...

I agree, it is confusing. I'm not sure why the distinction between 'dynamic' and 'test' is important. As a workaround you can try using `afterAny {}` or `beforeAny {}`. Discussed...

Would it be possible to get a Gradle Build Cache instance for Kotest? Then the cache could be shared for all developers, even on a fresh checkout. There are plugins...

There are a few other build-config fixes that will help improve build performance - enable parallel builds. Currently this is disabled. https://github.com/kotest/kotest/blob/ee33820b7d7f9382474853d7c0c75067600597ad/gradle.properties#L13 - enable configuration cache means faster project loading...

Could https://github.com/martinbonnin/vespene help with publishing? > Avoiding split repositories during upload by [creating a staging repository](https://support.sonatype.com/hc/en-us/articles/213465868-Uploading-to-a-Staging-Repository-via-REST-API) before upload and uploading all files to this staging repository.

> Thank you for your contribution! Before we ask the team responsible for this area to review your PR, could you please fix the commits history so the changes are...

@ov7a I asked for an explanation of what you meant, because I was confused, and I can see you sent me a screenshot of the commits page back. I'm now...

Thanks for the explanation @ljacomet. I see what you mean now. However, although I understand the documentation says otherwise, this style of commit was enforced by the DCO Bot, and...

Can you at least trigger some performance tests, if any exist that would measure the affected code?

K/N support is definitely possible. In principle all that's needed is to move the jsMain code that was added in https://github.com/charleskorn/kaml/pull/437 into commonMain. Hopefully it just works, with minimal changes.