I'm getting a 404 for the wasmJs artifacts for 5.9...

# kotest

[eygraber]

I'm getting a 404 for the wasmJs artifacts for 5.9.0 😢

https://repo.maven.apache.org/maven2/io/kotest/kotest-assertions-core-wasm-js/5.9.0/

[Oliver.O]

@Emil Kantis Something missing in the publishing process?

[eygraber]

Looks like https://github.com/kotest/kotest/blob/master/.github/workflows/release_base.yml#L32-37 needs to be updated

[eygraber]

https://github.com/kotest/kotest/pull/4010

[Emil Kantis]

Thanks, good catch 🙂

[Oliver.O]

Do we have the option of avoiding duplicating Gradle publishing targets and use something like publishAllPublicationsToDeployRepository instead?

[Emil Kantis]

only if we force all builds to build on macos, i suppose. ios/macos/watchos artifacts must be built on apple hardware... 🙂

[Oliver.O]

...which is slow, I guess, on the GitHub runners. OK, I understand the problem.

[eygraber]

The macos-14 is a little faster but still not close to the linux one. I think you can run publishAllPublicationsToDeployRepository on linux, and then the specific ones on macos-14 and windows-latest

[Emil Kantis]

wasm artifacts should be out now. Could you try again?

[eygraber]

Or...maybe not? I think I used to do that and ran into issues so I switched everything to publish from macos-14 but I don't remember the context.

I'm looking through my projects now to see if I can find anything.

[eygraber]

wasm artifacts should be out now. Could you try again?

Still 404 but there's some propagation time so I'll wait 10-30 minutes

[Oliver.O]

Earlier today it took way longer than 30 minutes for Maven Central to sync, more like hours. (And I'm not talking about Search, which will take another 4+ hours).

[Oliver.O]

OK, this time they proved me wrong. Artifacts showing up...

[Oliver.O]

@eygraber Does it work for you now?

[eygraber]

Yes!