diff --git a/README.md b/README.md
index b3279c0..4ef44bc 100644
--- a/README.md
+++ b/README.md
@@ -1,7 +1,7 @@
 # pkl-codegen
 A collection of docker images to generate code bindings for pkl models (in either Swift, Java, or Kotlin). Also supports PklDoc generation.
 
-Current builds are created for pkl version 0.29.0, 0.29.1, 0.30.0, 0.30.1, 0.30.2, 0.31.0 and 0.31.1.
+Current builds are created for pkl version 0.29.0, 0.29.1, 0.30.0, 0.30.1, 0.30.2, 0.31.0, 0.31.1 and 0.32.0.
 
 ## Usage
 Given an input model of `example.pkl`, you can generate a code binding for a selected platform and pkl version using the following command:
@@ -10,10 +10,10 @@ Given an input model of `example.pkl`, you can generate a code binding for a sel
 docker run --rm -v "./:/data" ghcr.io/emilymclean/pkl-codegen-<platform>:<version> /data/example.pkl -o /data/java
 ```
 
-So, for Kotlin using pkl version 0.31.1:
+So, for Kotlin using pkl version 0.32.0:
 
 ```sh
-docker run --rm -v "./:/data" ghcr.io/emilymclean/pkl-codegen-kotlin:0.31.1 /data/example.pkl -o /data/java
+docker run --rm -v "./:/data" ghcr.io/emilymclean/pkl-codegen-kotlin:0.32.0 /data/example.pkl -o /data/java
 ```
 
 The supported platforms/images are as follows:
@@ -27,4 +27,4 @@ The supported platforms/images are as follows:
 | PklDoc 	| `pkl-codegen-doc`    	|
 
 ### Versioning
-Versions of the container generally adhere to the following versioning format: `<pkl version>-<container release version>`. For example, for pkl `0.31.1` and release `1.0.0`, this would be `0.31.1-1.0.0`. In addition, a tag for the container major version, nightly version, and major+nightly version is also published. In the same circumstance as above, this would be `0.31.1-1`, `0.31.1-nightly`, and `0.31.1-1-nightly` respectively. It is **highly** recommended to at least pin to a major version to prevent breaking changes from accidentally interfering with use. 
\ No newline at end of file
+Versions of the container generally adhere to the following versioning format: `<pkl version>-<container release version>`. For example, for pkl `0.32.0` and release `1.0.0`, this would be `0.32.0-1.0.0`. In addition, a tag for the container major version, nightly version, and major+nightly version is also published. In the same circumstance as above, this would be `0.32.0-1`, `0.32.0-nightly`, and `0.32.0-1-nightly` respectively. It is **highly** recommended to at least pin to a major version to prevent breaking changes from accidentally interfering with use. 
\ No newline at end of file
diff --git a/pkl-versions b/pkl-versions
index c51105a..a31258c 100644
--- a/pkl-versions
+++ b/pkl-versions
@@ -5,3 +5,4 @@
 0.30.2
 0.31.0
 0.31.1
+0.32.0