-
Notifications
You must be signed in to change notification settings - Fork 92
Publish for 2.13.0-RC2 #311
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I hit "close" and "release" in the Sonatype web UI let's keep an eye on https://repo1.maven.org/maven2/org/scala-lang/modules/scala-xml_2.13.0-RC2/1.2.0/ |
gah, the staging repos contained 2.11, 2.12, and 2.13.0-RC2 artifacts, so when I released them, Sonatype refused to release any of them, since the 2.11 and 2.12 artifacts were duplicates. I had thought it would let the 2.13.0-RC2 ones go forward anyway can you delete and re-push the RC2-only tag? |
Weird, I guess there's something wrong with the publish script. I'll try to just build RC2 artifacts in Travis. |
I see staging repos (I don't get notified, but I happened to look) they contain only RC2 artifacts 👍 I hit "close" and "release" let's keep an eye on https://repo1.maven.org/maven2/org/scala-lang/modules/scala-xml_2.13.0-RC2/1.2.0/ |
|
A tag was pushed for 1.2.0:
https://github.com/scala/scala-xml/releases/tag/v1.2.0%232.13.0-RC2%238
Artifacts for 2.13.0-RC2 should have shown up in Sonatype.
The text was updated successfully, but these errors were encountered: