Skip to content

Commit

Permalink
chore: remove 2.12.8 and 2.12.9 publishing
Browse files Browse the repository at this point in the history
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.
  • Loading branch information
ckipp01 committed Oct 10, 2022
1 parent 655ab7d commit b30daff
Show file tree
Hide file tree
Showing 2 changed files with 1 addition and 5 deletions.
2 changes: 0 additions & 2 deletions bin/test-release.sh
Original file line number Diff line number Diff line change
Expand Up @@ -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 \
Expand Down
4 changes: 1 addition & 3 deletions build.sbt
Original file line number Diff line number Diff line change
Expand Up @@ -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(
Expand Down

0 comments on commit b30daff

Please sign in to comment.