github gives us 422 when using Scala 3.0.0-M3

[hedefalk]

We're trying a Scala 3 upgrade and were having problems publishing to github packages when our Scala version is "3.0.0-M3", getting 422 responses.

2.13 works fine:

[info] published iam-policy_2.13 to https://maven.pkg.github.com/OurOrg/iam-policy/rat/iam-policy_2.13/1.0.1-RC1/iam-policy_2.13-1.0.1-RC1.pom

while pushing these with "3.0.0-M3" fails with 422:

[error] java.io.IOException: Server returned HTTP response code: 422 for URL: https://maven.pkg.github.com/OurOrg/iam-policy/rat/iam-policy_3.0.0-M3/2.0.0-RC2/iam-policy_3.0.0-M3-2.0.0-RC2.pom

The only thing I seem to see plausible is some kind of github-specific semver check breaking because of the '-' in the artifact name that's not there in 2.13.

Is there any known workaround or am I missing something obvious?

[labra]

The same is happening for us trying to publish scala-3.0.0-RC2 in this repo.

I wonder if this is related with the suffix RC2 similar to using SNAPSHOTS as in this issue #23

[djspiewak]

This is fascinating! I don't think it's a semver check because I've successfully published hash-snapshot artifacts to github packages. I'll investigate further, but unfortunately my guess is a bug on their end.

[labra]

Do you know if there are other repos which are able to publish scala-3.0.0-RC2 githup packages?