Adjust build definition and CI process

- remove `scalaModuleMimaPreviousVersion` (already set by sbt-version-policy)
- add `scalaModuleAutomaticModuleName` (required by sbt-scala-module 2.3+)
- add `versionPolicyIntention`
- invoke `versionCheck` before publishing a release

Fixes #72
Fixes #15

Author: julienrf

build.sbt

@@ -18,7 +18,8 @@ lazy val scalaLibraryNext = crossProject(JVMPlatform, JSPlatform)
   .jsEnablePlugins(ScalaJSJUnitPlugin)
   .settings(
     ScalaModulePlugin.scalaModuleSettings,
-    scalaModuleMimaPreviousVersion := None,
+    scalaModuleAutomaticModuleName := Some("scala.library.next"),
+    versionPolicyIntention := Compatibility.None, // TODO Change to `Compatibility.BinaryAndSourceCompatible` after the first release
     scalacOptions ++= Seq("-deprecation", "-feature", "-Werror"),
     libraryDependencies ++= Seq(
       "org.scalacheck" %%% "scalacheck" % "1.15.4" % Test,

build.sh

@@ -34,6 +34,7 @@ verPat="[0-9]+\.[0-9]+\.[0-9]+(-[A-Za-z0-9-]+)?"
 tagPat="^v$verPat(#.*)?$"
 
 if [[ "$TRAVIS_TAG" =~ $tagPat ]]; then
+  versionCheckTask="versionCheck"
   releaseTask="ci-release"
   if ! isReleaseJob; then
     echo "Not releasing on Java $ADOPTOPENJDK with Scala $TRAVIS_SCALA_VERSION"
@@ -50,4 +51,4 @@ export CI_SNAPSHOT_RELEASE="${projectPrefix}publish"
 # for now, until we're confident in the new release scripts, just close the staging repo.
 export CI_SONATYPE_RELEASE="; sonatypePrepare; sonatypeBundleUpload; sonatypeClose"
 
-sbt clean ${projectPrefix}test ${projectPrefix}publishLocal $releaseTask
+sbt clean ${projectPrefix}test ${projectPrefix}publishLocal $versionCheckTask $releaseTask