v0.6.3

5 files changed, 21 insertions, 21 deletions

diff --git a/documentation/book/the_lux_programming_language/appendix_h.md b/documentation/book/the_lux_programming_language/appendix_h.md
index c2ce1ba28..9d0cf5f90 100644
--- a/documentation/book/the_lux_programming_language/appendix_h.md
+++ b/documentation/book/the_lux_programming_language/appendix_h.md
@@ -43,9 +43,9 @@ lux deps
 
 =>
 
-[?] Fetching com.github.luxlang:lux-jvm-0.6.2 from "~/.m2/repository"
-[O] Found com.github.luxlang:lux-jvm-0.6.2 at "~/.m2/repository"
- Local successes: 0: "com.github.luxlang:lux-jvm-0.6.2"
+[?] Fetching com.github.luxlang:lux-jvm-0.6.3 from "~/.m2/repository"
+[O] Found com.github.luxlang:lux-jvm-0.6.3 at "~/.m2/repository"
+ Local successes: 0: "com.github.luxlang:lux-jvm-0.6.3"
   Local failures: 
 Remote successes: 
  Remote failures:
@@ -124,7 +124,7 @@ Now that we have seen the available commands, it would be useful to see an annot
  [... An optional identity for the project.
   ... It can also be specified or overriden in a non-default profile.
   ... This will be the name given to the project when installed/deployed as a dependency.
-  "identity" ["com.github.luxlang" "stdlib" "0.6.2"]
+  "identity" ["com.github.luxlang" "stdlib" "0.6.3"]
 
   ... Every piece of information, and the whole "info" bundle, are optional.
   "info" ["url" "https://github.com/LuxLang/lux"
@@ -163,36 +163,36 @@ Now that we have seen the available commands, it would be useful to see an annot
  ... The following are alternative profiles to use in various situations.
  "jvm"
  [... "compiler" specifies the dependency to fetch and use as the compiler.
-  "compiler" ["com.github.luxlang" "lux-jvm" "0.6.2" "jar"]
+  "compiler" ["com.github.luxlang" "lux-jvm" "0.6.3" "jar"]
   ... "dependencies" is an optional list of dependencies to fetch.
   ... The dependencies have the same shape as when specifying the compiler.
   ... When omitting the packaging format of the dependency, "tar" will be assumed.
   ... "dependencies" [["org.ow2.asm" "asm-all" "5.0.3" "jar"]
-  ...                 ["com.github.luxlang" "stdlib" "0.6.2"]]
+  ...                 ["com.github.luxlang" "stdlib" "0.6.3"]]
   ... The OS command to use when running JVM tests. The default is described below.
   ... "java" ["java" "-jar"]
   ]
 
  "js"
- ["compiler" ["com.github.luxlang" "lux-js" "0.6.2" "js"]
+ ["compiler" ["com.github.luxlang" "lux-js" "0.6.3" "js"]
   ... The OS command to use when running JS tests. The default is described below.
   ... "js" ["node" "--stack_size=8192"]
   ]
 
  "python"
- ["compiler" ["com.github.luxlang" "lux-python" "0.6.2" "jar"]
+ ["compiler" ["com.github.luxlang" "lux-python" "0.6.3" "jar"]
   ... The OS command to use when running Python tests. The default is described below.
   ... "python" ["python3"]
   ]
 
  "lua"
- ["compiler" ["com.github.luxlang" "lux-lua" "0.6.2" "jar"]
+ ["compiler" ["com.github.luxlang" "lux-lua" "0.6.3" "jar"]
   ... The OS command to use when running Lua tests. The default is described below.
   ... "lua" ["lua"]
   ]
 
  "ruby"
- ["compiler" ["com.github.luxlang" "lux-ruby" "0.6.2" "jar"]
+ ["compiler" ["com.github.luxlang" "lux-ruby" "0.6.3" "jar"]
   ... The OS command to use when running Ruby tests. The default is described below.
   ... "ruby" ["ruby"]
   ]
diff --git a/documentation/book/the_lux_programming_language/chapter_1.md b/documentation/book/the_lux_programming_language/chapter_1.md
index 1660069fa..15bf9501b 100644
--- a/documentation/book/the_lux_programming_language/chapter_1.md
+++ b/documentation/book/the_lux_programming_language/chapter_1.md
@@ -43,8 +43,8 @@ These are the steps:
   "repositories" ["https://oss.sonatype.org/content/repositories/snapshots/"
                   "https://oss.sonatype.org/service/local/staging/deploy/maven2/"]
   
-  "dependencies" [["com.github.luxlang" "stdlib" "0.6.2" "tar"]]
-  "compiler" ["com.github.luxlang" "lux-jvm" "0.6.2" "jar"]
+  "dependencies" [["com.github.luxlang" "stdlib" "0.6.3" "tar"]]
+  "compiler" ["com.github.luxlang" "lux-jvm" "0.6.3" "jar"]
 
   "program" "main"]]
 
diff --git a/documentation/book/the_lux_programming_language/chapter_16.md b/documentation/book/the_lux_programming_language/chapter_16.md
index 2eb17dac9..7945004c6 100644
--- a/documentation/book/the_lux_programming_language/chapter_16.md
+++ b/documentation/book/the_lux_programming_language/chapter_16.md
@@ -22,7 +22,7 @@ Let's take a look at the `project.lux` file for the Lux standard library itself.
 
 ```clojure
 [""
- ["identity" ["com.github.luxlang" "stdlib" "0.6.2"]
+ ["identity" ["com.github.luxlang" "stdlib" "0.6.3"]
 
   "deploy_repositories" ["snapshots" "https://oss.sonatype.org/content/repositories/snapshots/"
                          "releases" "https://oss.sonatype.org/service/local/staging/deploy/maven2/"]
@@ -31,7 +31,7 @@ Let's take a look at the `project.lux` file for the Lux standard library itself.
                   "https://oss.sonatype.org/service/local/staging/deploy/maven2/"]]
 
  "jvm"
- ["compiler" ["com.github.luxlang" "lux-jvm" "0.6.2" "jar"]]
+ ["compiler" ["com.github.luxlang" "lux-jvm" "0.6.3" "jar"]]
 
  "bibliotheca"
  ["info" ["description" "Standard Library for the Lux programming language."]
diff --git a/documentation/book/the_lux_programming_language/chapter_17.md b/documentation/book/the_lux_programming_language/chapter_17.md
index bbf383151..31f5d74df 100644
--- a/documentation/book/the_lux_programming_language/chapter_17.md
+++ b/documentation/book/the_lux_programming_language/chapter_17.md
@@ -68,14 +68,14 @@ In order to compile a Lux program to any of these alternative platforms, you mus
 
 An Aedifex `project.lux` file allows for a `"compiler"` option to specify (as a dependency) the compiler you wish to use.
 
-This option can be omitted, in which case it will pick, as a default value: `["com.github.luxlang" "lux-jvm" "0.6.2" "jar"]`.
+This option can be omitted, in which case it will pick, as a default value: `["com.github.luxlang" "lux-jvm" "0.6.3" "jar"]`.
 
 Here are the compilers for the alternative platforms:
 
-* For JavaScript: `["com.github.luxlang" "lux-js" "0.6.2" "js"]`
-* For Python: `["com.github.luxlang" "lux-python" "0.6.2" "jar"]`
-* For Lua: `["com.github.luxlang" "lux-lua" "0.6.2" "jar"]`
-* For Ruby: `["com.github.luxlang" "lux-ruby" "0.6.2" "jar"]`
+* For JavaScript: `["com.github.luxlang" "lux-js" "0.6.3" "js"]`
+* For Python: `["com.github.luxlang" "lux-python" "0.6.3" "jar"]`
+* For Lua: `["com.github.luxlang" "lux-lua" "0.6.3" "jar"]`
+* For Ruby: `["com.github.luxlang" "lux-ruby" "0.6.3" "jar"]`
 
 You don't need to use any special command on Aedifex in order to compile Lux to any alternative platform.
 
@@ -193,7 +193,7 @@ However, it is possible to specify that a file contains code that is only meant
 * For Lua: `foo.lua.lux`
 * For Ruby: `foo.rb.lux`
 
-If you're using, let's say, the JavaScript compiler for Lux (i.e. `["com.github.luxlang" "lux-js" "0.6.2" "js"]`), whenever you import a module as a dependency, the compiler will first look for a file with the `.js.lux` extension, and if it fails to find one, it will look for a file with the plain `.lux` extension.
+If you're using, let's say, the JavaScript compiler for Lux (i.e. `["com.github.luxlang" "lux-js" "0.6.3" "js"]`), whenever you import a module as a dependency, the compiler will first look for a file with the `.js.lux` extension, and if it fails to find one, it will look for a file with the plain `.lux` extension.
 
 _What happens if I do not have a `.js.lux` file, but I do have files with the other special extensions?_
 
diff --git a/documentation/book/the_lux_programming_language/conclusion.md b/documentation/book/the_lux_programming_language/conclusion.md
index b5394e9e9..a7a0bb007 100644
--- a/documentation/book/the_lux_programming_language/conclusion.md
+++ b/documentation/book/the_lux_programming_language/conclusion.md
@@ -14,7 +14,7 @@ My mission with Lux has been (and continues to be) to create a language that max
 
 Lux is still in its adolescence.
 
-What you have learned is Lux version 0.6.2.
+What you have learned is Lux version 0.6.3.
 
 In future releases, much more power will be added to the language, more platforms will be within reach of Lux programmers, and better performance will be achieved, with little to no effort on the side of programmers.