Skip to content

Commit 29b548e

Browse files
committed
add Scala 2.12.14 to CI matrix
1 parent a4e6048 commit 29b548e

File tree

2 files changed

+5
-1
lines changed

2 files changed

+5
-1
lines changed

.travis.yml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -60,6 +60,10 @@ env:
6060
TRAVIS_JDK=adopt@~1.8.0-0
6161
- SCALA_VERSION=2.12.13
6262
TRAVIS_JDK=adopt@~1.11.0-0
63+
- SCALA_VERSION=2.12.14
64+
TRAVIS_JDK=adopt@~1.8.0-0
65+
- SCALA_VERSION=2.12.14
66+
TRAVIS_JDK=adopt@~1.11.0-0
6367
#
6468
# Scala 2.13 supported versions
6569
#

RELEASING.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,4 +13,4 @@ It is often the case when this compiler plugin needs to be released for a newly
1313
* master, if no features or bug fixes were merged to master since the latest release
1414
* tag, if the master has unreleased features or bug fixes. In this case you will need to cherry pick the commit that adds support for the new Scala version.
1515
1. Create a file `version.sbt` containing `version in ThisBuild := "0.11"` which sets the version to be back-released. This will override the automatic version derivation from the git history. Alternatively you can `set version in ThisBuild := ...` in the command line.
16-
1. Publish the release by running `SONATYPE_USERNAME=xxx SONATYPE_PASSWORD=xxx sbt clean ++2.12.13 publishSigned sonatypeBundleRelease` (with the appropriate credentials and scala version). You will need Sonatype OSS repository rights to publish under `com.typesafe` organisation.
16+
1. Publish the release by running `SONATYPE_USERNAME=xxx SONATYPE_PASSWORD=xxx sbt clean ++2.12.14 publishSigned sonatypeBundleRelease` (with the appropriate credentials and scala version). You will need Sonatype OSS repository rights to publish under `com.typesafe` organisation.

0 commit comments

Comments
 (0)