-
Notifications
You must be signed in to change notification settings - Fork 17
roll a new release #14
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
This reverts commit 9163011. Now I'm not sure what's right, e.g. http://www.scala-sbt.org/0.13/docs/Bintray-For-Plugins.html seems to suggest using None, except I'm not sure if we're supposed to be taking advantage of "If you’re a member of the sbt organization on bintray" or not... we can take it up on #14
1.0.5 is tagged. @retronym I took a stab at publishing it, too, but I'm a Bintray newbie (I know Sonatype well now but have not done Bintray before, that I can recall anyway) and I think I may have published 1.0.5 to the wrong place, or maybe it's a right place but not the usual right place? 1.0.5 artifacts are at https://dl.bintray.com/typesafe/sbt-plugins/org.scala-lang.modules/scala-module-plugin/scala_2.10/sbt_0.13/ but that isn't where the other versions were published rather than fumble around with it more myself, I'm hoping you might remember how this is supposed to work in this repo |
I remember being confused myself. https://bintray.com/adriaanm/sbt-plugins/scala-module-plugin |
Released 1.0.6 and updated the README with instructions how to cut a release. |
so we can push the MiMa version bump (#15) out to the modules
The text was updated successfully, but these errors were encountered: