Closed jacobras closed 7 months ago
Let's merge it, and try to release a new version
Could you perform it by checking out the code in the publish job?
I would prefer it. As if build fails it will be easier to check.
These things can be annoying to test 😅 I did a publishKotlinMultiplatformPublicationToMavenLocal
on my machine just to check basic compilation but that's not the hardest part of publishing.
Yes, i. know...
BTW, the release job failed because an "unauthenticated" request to sonatype... :S
The current 401 on the URL seems to be getting us a step further. How old is your Sonatype account? Did you see the post-2021 configuration at https://github.com/gradle-nexus/publish-plugin#publishing-to-maven-central-via-sonatype-ossrh?
Couple of pointers on https://central.sonatype.org/faq/401-error/ might be useful as well.
P.S. I'm in the Kotlin slack @alorma , if you're also there we could chat quicker.
Jobs inside a workflow run in parallel, so the publishing one never got any build output or even code. With this change there's just one
publish
job that checks out, builds and publishes. (The right build gets triggered automatically as a dependency from the publishing command).