-
Notifications
You must be signed in to change notification settings - Fork 131
publish for Scala 2.13.0-M5 #170
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
okay so first we need to assess what version we are publishing and what changes need to be included we would prefer to just republish 1.1.1 for M5 rather than have to go to 1.1.2. can we do that? the Scala 2.13 community build is just using the plain 1.1.x branch, so that's a good sign looking at but I don't see any commits we need to include except for the M5 version bumps (#168, 61da24e) so I think we can just cherry-pick 61da24e onto the I'll try it. |
I did:
this resulted in https://travis-ci.org/scala/scala-parser-combinators/builds/427431583 of which the JDK 8 job is https://travis-ci.org/scala/scala-parser-combinators/jobs/427431586 but then something went wrong in the JDK 6 job (https://travis-ci.org/scala/scala-parser-combinators/jobs/427431584) and it ran on Java 8 not 6, so both jobs published stuff to staging. I think the safest course is to delete those staging repos, fix the cause of the JDK version problem, then start again. |
staging repos (orgscala-lang-1603 and orgscala-lang-1604) dropped via Sonatype web UI (as user
|
as for why the JDK 6 job ran on JDK 8, I thought we addressed that already at #156 the job log says
oh, I know, #156 is part of the |
ok so from the same shell prompt as before I did
the new build on Travis is https://travis-ci.org/scala/scala-parser-combinators/builds/427437124 the JDK 6 job, https://travis-ci.org/scala/scala-parser-combinators/jobs/427437125, now says and the JDK 8 job, https://travis-ci.org/scala/scala-parser-combinators/jobs/427437126, staged artifacts to Sonatype 👍 as usual it's nondeterministic how many staging repos we end up with. this time the JVM artifacts ended up in orgscala-lang-1605, the JS artifacts in orgscala-lang-1606 I closed both repos via the Sonatype web UI. I'll sanity check the artifacts before actually releasing them |
made a blank sbt project with just:
and verified that resolution fails: then I added
and re-tried and got:
then I ran
so looks like we're good. |
I hit "release" on both staging repos in the Sonatype web UI, so the artifacts should show up on Maven Central soon 🚀 watch this space: https://repo1.maven.org/maven2/org/scala-lang/modules/scala-parser-combinators_2.13.0-M5/1.1.1/ |
for reference, here's how M4 publishing went down: #151
version bumping for M5 happened at #168
The text was updated successfully, but these errors were encountered: