diff --git a/planck-c/globals.h b/planck-c/globals.h
index 5e13bf64..cd5b974b 100644
--- a/planck-c/globals.h
+++ b/planck-c/globals.h
@@ -1,6 +1,6 @@
 // Global variables used throughout Planck
 
-#define PLANCK_VERSION "2.1.0"
+#define PLANCK_VERSION "2.2.0"
 
 #define EXIT_SUCCESS_INTERNAL -257
 
diff --git a/site/src/performance.md b/site/src/performance.md
index 505f1f1f..21363c5c 100644
--- a/site/src/performance.md
+++ b/site/src/performance.md
@@ -40,7 +40,7 @@ The caching mechanism works whether your are running `planck` to execute a scrip
 Planck uses a (naïve) file timestamp mechanism to know if cache files are stale, and it additionally looks at comments like the following
 
 ```
-// Compiled by ClojureScript 1.9.473 {:static-fns true, :elide-asserts true}
+// Compiled by ClojureScript 1.9.494 {:static-fns true, :elide-asserts true}
 ```
 
 in the compiled JavaScript to see if the files are applicable. If a file can’t be used, it is replaced with an updated copy.
diff --git a/site/src/repl.md b/site/src/repl.md
index 867c27a6..9989eceb 100644
--- a/site/src/repl.md
+++ b/site/src/repl.md
@@ -5,8 +5,8 @@ If you don't provide any `-i` or `-e` options or args to `planck` when launching
 
 ```
 $ planck
-Planck 2.1.0
-ClojureScript 1.9.473
+Planck 2.2.0
+ClojureScript 1.9.494
     Docs: (doc function-name-here)
           (find-doc "part-of-name-here")
   Source: (source function-name-here)