I tried using kotest 4.1.0.RC2 in an MPP project. ...

# kotest-contributors

[AJ Alt]

I tried using kotest 4.1.0.RC2 in an MPP project. It looks like the mingwX64 artifact isn't being published (https://repo1.maven.org/maven2/io/kotest/). I'm able to run the publish task locally on Windows, and I see it being published for snapshots ( https://oss.sonatype.org/content/repositories/snapshots/io/kotest/kotest-assertions-core-mingwx64/). Did a step get missed when promoting the artifacts in sonatype?

[sam]

Aha. We only publish from my ubuntu box 🙂

[LeoColman]

Does every artifact needs to be individually published in Sonatype?

[LeoColman]

I thought the whole bundle got through

[sam]

It's because my linux machine won't generate artifacts for mac or win

[sam]

We would need to move the publication step to github actions

[LeoColman]

ah, it makes sense

[AJ Alt]

The build.yml action already exists to do that. Are you not using it?

[sam]

the build workflow will publish to snapshots, it's not handling releases

[sam]

We'll add to add in the pgp key signing step, and put the key somewhere in secrets, generate the javadoc and sources jars, and then publish to sonatype. I can still do the final "release" step in the sonatype ui

[sam]

There goes my Friday 😂

[AJ Alt]

That's what I do for clikt: https://github.com/ajalt/clikt/blob/3af97bb0b15ee8c600fa3cbb353880341d99b897/.github/workflows/publish.yml#L78

[AJ Alt]

I use the same action for snapshots and releases

[AJ Alt]

Then use the sonatype UI to manually promote in the release case

[sam]

Seems like the least hassle approach

[sam]

I'm going to be releasing 4.1.0 final tonight or tomorrow or sunday. I'll make sure this is in place for that.

[sam]

working on hoplite right now 🙂