Hey everyone, just wanted to give a quick update. ...

# ballast

[Casey Brooks]

Hey everyone, just wanted to give a quick update. I’ve been trying to get a Ballast 5.0.0 release out for a while, but have had the hardest time getting the publication working correctly with the new MavenCentral system. I finally got the whole process working a few days ago, but it seems like many of the artifacts did not sync properly to MavenCentral, and I’m not entirely sure why. So please ignore the 5.0.0 version which is currently on MavenCentral; it is incomplete and I will need to use a different version number for an actual release. I am really trying to get this out by the end of the year, if I can get the new MavenCentral publishing system to work correctly, and will be posting here soon with another update once I get it figured out.

In the meantime, you can still use the 4.2.2-SNAPSHOT version from https://central.sonatype.com/repository/maven-snapshots/ to try out the latest build which targets Kotlin 2.2.20.

[CLOVIS]

Hey! What are you using to publish? Throughout this mess I've migrated to NMCP and I've not had any issues since

[Casey Brooks]

Nice find, I’ll give that plugin a try if I can’t get my current option figured out.

I tried several different plugins, but had issues with them for various reasons. In particular, I’ve got the CI set up to publish artifacts from different pipeline jobs (iOS artifacts from Macos runners, everything else from Ubuntu runners) rather than everything built and published in the same job. Many of the options I looked into didn’t seem to support this workflow, so for a long time now, I’ve manually called the Sonatype APIs needed to create and release the staging repo. I have reimplemented that workflow with the new OSSRH Staging API and feel like I’ve got it ~95% of the way there, but this last 5% seems like reliability issues with the OSSRH compatibility service itself, not issues with my configuration. I’m hoping I can get this figured out, though, without having to throw it away and try the NMCP plugin or rewrite the workflow to use the Portal Publisher API.

[CLOVIS]

I’ve got the CI set up to publish artifacts from different pipeline jobs (iOS artifacts from Macos runners, everything else from Ubuntu runners) rather than everything built and published in the same job.

Just in case you're not aware, that's not necessary anymore, you can compile all targets, including macOS, on the Linux runners. You still can't run there, but that's not needed for publishing.

[Robert Jaros]

OSSRH compatibility layer is crap ;] It's just not working stable enough for big projects.