A modern programming language that makes developers happier.

kotlinlang

<@U54CM9PGS> did you get any feedback on the 5.9 snapshots? I think it'd be nice to publish 5.9.0 soon :slightly_smiling_face:

No feedback so far. Which is probably neutral (no one tried) or a good sign (nothing to complain). However, I still have a test with one of my projects on my list. I like the idea of publishing 5.9.0 soon. :rocket: Would it be sufficient for that if I report back by tomorrow night?

No rush, just let me know when you had the chance to try it out :slightly_smiling_face:

I'll test some projects with it as well.. but I don't have anything that does very exotic stuff

We can always release and fix forward :slightly_smiling_face:

I tried snapshot build w/ a multiplatform project and a bigger regular jvm backend project, no issues.

Completed my homework: Tested Kotest `5.9.0.1444-SNAPSHOT` with a Multiplatform JVM/JS project on Kotlin 2.0.0-RC1 and 2.0.0-RC2, no issues. :white_check_mark:

The `io.kotest.multiplatform` Gradle plugin (`io.kotest:kotest-framework-multiplatform-plugin-gradle`) is not published to the snapshot repo, right? Is this intentional?

I noticed the same thing. I guess the gradle plugin publishing doesn’t include a snapshot for publishing configuration? 

If you want some more feedback, I used `5.9.0.1440-SNAPSHOT` on Kotlin 1.9.23 in my mordant and clikt libraries to add wasm support, and I didn't run into any issues.

I got two small PRs up, could someone give them a look before I start the release? :slightly_smiling_face: 

Regarding the missing Gradle plugin in snapshots, I've added <https://github.com/kotest/kotest/issues/4012>.

<@UVAR0DXP0> Do you think the suggestion there is safe to try?

<https://github.com/kotest/kotest/blob/master/.github/workflows/release_multiplatform_plugin_gradle.yml>

Any difference between `publish` and `publishPlugins`?

I was under the impression that since `publishPlugins` is part of the "plugin portal" group, it is a different beast for the Gradle plugin repo. In contrast, `publish` is just the ordinary task which publishes the artifact (in this case, our plugin) to wherever the other publications go. Like, when I do `publishToMavenLocal`, the Gradle plugin gets published as well. But that's just my guess, and I find the Gradle docs on publishing overwhelming (as usual with anything Gradle).