-
Notifications
You must be signed in to change notification settings - Fork 18
2.12.x series artifact #14
Comments
publishing of artifacts is tag-driven. you push a version tag and Travis runs are you ready to publish version 1.0.3? if so, go ahead. if you want to republish a previously published version, just for a new Scala milestone, we'd need to do some work to support that; see scala/sbt-scala-module#12 in this particular case, since the publishing stuff has all changed since 1.0.2 and it'll be the first time we're trying the new stuff in this particular repo, I guess I'd suggest going ahead and publishing 1.0.3 and if there aren't supposed to be any user-visible changes since 1.0.2, say so in the release notes. |
@SethTisue I see 2.12.0-RC1 coming soon, so I decided to publish 1.0.3 after Scala release candidate is out. |
Also, it is reasonable to adjust build script like here scala/scala-parser-combinators@cdfba62 |
yes, I think so |
@SethTisue done. I see 2.12.0-RC2 coming (month and a half passed, eh), seems reasonable to publish a new RC of scala-continuations with it |
sounds good |
@SethTisue just pushed 1.0.3-RC3 tag, artifacts seems to be staged. |
I see messages like this in build log |
I see 2.11.8 and 2.12.0-RC2 artifacts at https://oss.sonatype.org/content/repositories/orgscala-lang-1350/org/scala-lang/plugins/ and https://oss.sonatype.org/content/repositories/orgscala-lang-1349/org/scala-lang/plugins/. Happy to promote both to maven central! |
I have unleashed them! Onwards to Maven Central! |
@adriaanm thanks! |
@adriaanm I just updated scala-continuations to build against scala 2.12.0-M5, it works fine in my cases. What I have to do exactly to make apropriate artifact be published?
The text was updated successfully, but these errors were encountered: