Release 0.4.0

Might make sense to release 0.4.0 by now, it’s been a long time since 0.3.0 with more than 100 commits since then.

• A milestone exists for the release you are about to perform. If it doesn’t create one.
• x The milestone due date is the day of the release.
• Travis passes against latest Scala versions (past example: https://github.com/lightbend/mima/pull/164)
• All tickets fixed in the current development cycle are associated to the current milestone.
• Bump the version in the README.md and git commit.
• Run clean. (particularly if you’ve recently bumped scalaVersion - see #191)
• Create an annotated, signed git tag (git tag -a -s) and push it. The name of the tag should follow the format of previous tags (not ‘v’ prefix). reload and verify that show version in sbt picks up the version number from the tag.
• Run ^publishSigned. You should start seeing “published mima-… to https://oss.sonatype.org/service/local/staging/deploy/maven2/…”
• Login on Sonatype and follow this guide to release the staged MiMa artifacts.
• Login to Bintray and publish sbt plugin artifacts. (or use sbtplugin/bintrayRelease)
• Wait for artifacts to show up on Maven Central
  • sbt plugin jar and dependent jars resolvable by sbt
  • virtual directory appears: https://repo1.maven.org/maven2/com/typesafe/mima-core_2.12/0.3.0/
• Close milestone
• Add release notes to tag
• Hit “Publish Release” on GitHub
• Announce the release in the Announce category of Scala Users (e.g https://users.scala-lang.org/t/announcing-mima-migration-manager-0-3-0/2782)

[adriaanm]

How about now? 😄

[dwijnand]

Funny you, specifically, should mention it, because I’ve got a fix for your https://github.com/lightbend/migration-manager/issues/201 cooking. 😄