You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: RELEASING.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -15,6 +15,6 @@ It is often the case when this compiler plugin needs to be released for a newly
15
15
* master, if no features or bug fixes were merged to master since the latest release
16
16
* 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.
17
17
2. 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.
18
-
3. Change the Scala version to the release you want to perform, this is done by `++2.12.9` in the sbt command line.
18
+
3. Change the Scala version to the release you want to perform, this is done by `++2.12.10` in the sbt command line.
19
19
4. Publish the release by running `sbt publishSigned`. You will need Sonatype OSS repository rights to publish under `com.typesafe` organisation.
20
20
5. Login to [Sonatype](https://oss.sonatype.org/) to close and release the repository.
0 commit comments