From b30daffc9753cede562b3329ffa21af075070121 Mon Sep 17 00:00:00 2001 From: Chris Kipp Date: Mon, 10 Oct 2022 14:59:54 +0200 Subject: [PATCH] chore: remove 2.12.8 and 2.12.9 publishing If someone is updating to the newest scoverage and are still on 2.12.8 or 2.12.9 there is no reason for them to not be able to bump their Scala version. There is no need to keep publishing all of these. I hit on this in publishing since scalameta wasn't published for 2.12.8 and the release failed because of it. --- bin/test-release.sh | 2 -- build.sbt | 4 +--- 2 files changed, 1 insertion(+), 5 deletions(-) diff --git a/bin/test-release.sh b/bin/test-release.sh index 29abd593..a81b978a 100755 --- a/bin/test-release.sh +++ b/bin/test-release.sh @@ -4,8 +4,6 @@ set -eux version=$1 coursier fetch \ - org.scoverage:scalac-scoverage-plugin_2.12.8:$version \ - org.scoverage:scalac-scoverage-plugin_2.12.9:$version \ org.scoverage:scalac-scoverage-plugin_2.12.10:$version \ org.scoverage:scalac-scoverage-plugin_2.12.11:$version \ org.scoverage:scalac-scoverage-plugin_2.12.12:$version \ diff --git a/build.sbt b/build.sbt index 36b1ca74..2ad28e0d 100644 --- a/build.sbt +++ b/build.sbt @@ -15,9 +15,7 @@ lazy val bin212 = "2.12.13", "2.12.12", "2.12.11", - "2.12.10", - "2.12.9", - "2.12.8" + "2.12.10" ) lazy val bin213 = Seq(