From 85083c5153b481b262550b88dbe899afd378ee73 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C5=81ukasz=20Wro=C5=84ski?= Date: Thu, 29 Sep 2022 14:28:16 +0200 Subject: [PATCH] Dump scala 2 version in docs --- website/docs/cookbooks/scala-versions.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/website/docs/cookbooks/scala-versions.md b/website/docs/cookbooks/scala-versions.md index a3d60ac5e2..9832ea4d47 100644 --- a/website/docs/cookbooks/scala-versions.md +++ b/website/docs/cookbooks/scala-versions.md @@ -75,11 +75,11 @@ and this: scala-cli -S 2.12 ScalaVersion.scala ``` -In the first example (`-S 2`), the application picks up the latest Scala 2 stable release (`2.13.7` at the time of this writing). -In the second example, the application picks up the latest stable release of `2.12` (which is `2.12.16` at the time of this writing). +In the first example (`-S 2`), the application picks up the latest Scala 2 stable release (`2.13.9` at the time of this writing). +In the second example, the application picks up the latest stable release of `2.12` (which is `2.12.17` at the time of this writing). You can also pin the version of the language within a `.scala` file with `using` directives. @@ -103,10 +103,10 @@ scala-cli ScalaVersion.scala version.scala ``` -The output at the time of this writing is "`2.12.16`". +The output at the time of this writing is "`2.12.17`". The `scala-cli` philosophy is “command line first,” so any configuration information that’s passed to the command line will override `using` directives. So when you run this command with the `-S` option: