Artifacts missing on Maven Central (including 3.1.3-RC1)

I can’t really figure out what’s going on here, but I have a script that is supposed to run every night to grab the newest nightly and then run some code with it. However, last night and today it’s failing due to not being able to resolve a scala version that says is published and is located in the maven-metadata.xml, but the artifacts aren’t there.

According to this release, 3.1.3-RC1-bin-20220406-73cda0c-NIGHTLY was successfully published and according to https://repo1.maven.org/maven2/org/scala-lang/scala3-compiler_3/maven-metadata.xml it should be the newest valid 3.1.3* version. However, if you look at the listing on here, the artifacts aren’t there. You can see that it won’t resolve with:

cs fetch org.scala-lang:scala3-compiler_3:3.1.3-RC1-bin-20220406-73cda0c-NIGHTLY

I know this isn’t the newest version as 3.1.3-RC1-bin-20220406-3d1d299-NIGHTLY was published last night, but any idea what’s going on here as that artifact should be there?

[anatoliykmetyuk]

I agree with @ckipp01, the nightly version skipped is probably not going to be a problem, as long as we have the RCs version in order.

[ckipp01]

Just to be clear, I probably wouldn’t recommend spending a lot of time on this. While it’s an inconvenience if someone tries to grab those versions, I have a feeling that it will impact very very few people. I was only aware of it because CI in both https://github.com/ckipp01/dotty-error-index and https://github.com/scalameta/metals both failed that night since they both rely on pulling in the latest nightly. Since there are newer versions, it’s done with and isn’t really an issue. It’s up to you if you want to chase it down, but please don’t on my account.