diff --git a/.github/workflows/dist.yml b/.github/workflows/dist.yml
index a034abb..f185a00 100644
--- a/.github/workflows/dist.yml
+++ b/.github/workflows/dist.yml
@@ -11,7 +11,7 @@ jobs:
     if: "startsWith(github.ref, 'refs/tags/')"
     strategy:
       matrix:
-        python-version: ['3.7', '3.8', '3.9', '3.10', '3.11']
+        python-version: ['3.7', '3.8', '3.9', '3.10', '3.11', '3.12']
     steps:
       - uses: actions/checkout@v3
       - uses: actions/setup-python@v4
@@ -44,7 +44,7 @@ jobs:
     strategy:
       matrix:
         target: [x64, x86]
-        python-version: ['3.8', '3.9', '3.10', '3.11']
+        python-version: ['3.8', '3.9', '3.10', '3.11', '3.12']
     steps:
       - uses: actions/checkout@v3
       - uses: actions/setup-python@v4
diff --git a/Cargo.toml b/Cargo.toml
index 96adca5..be31c8a 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "flatterer"
-version = "0.19.9"
+version = "0.19.10"
 authors = ["David Raznick <kindly@gmail.com>"]
 edition = "2021"
 license = "MIT"
@@ -14,9 +14,9 @@ serde_json = { version = "1.0.83", features = ["preserve_order"] }
 pyo3 = { version = "0.18.3", features = ["extension-module", "eyre"] }
 eyre= "0.6.8"
 #libflatterer={path = "../libflatterer"}
-libflatterer="0.19.8"
+libflatterer="0.19.9"
 
-flatterer-web="0.19.8"
+flatterer-web="0.19.9"
 #flatterer-web={path = "../flatterer-web"}
 
 env_logger= "0.9.0"
diff --git a/docs/options.md b/docs/options.md
index cb33858..d6f0176 100644
--- a/docs/options.md
+++ b/docs/options.md
@@ -777,7 +777,7 @@ The number of threads used to process the data. Default to 1. If set to 0 will u
 
 Works best with new line delimited JSON `--ndjson` as JSON parsing can then be done by each thread. This can about a x3 times improvement with 6 threads if you have that many CPU cores. Without `--ndjson` makes only about x1.24 improvement on 2 threads and not worth going over 2 as it will not lead to performance improvement. For very small datasets (less than 100 object) using threads will most likely be slower.
 
-**Warning:** Will fail for small inputs where the amount of objects is less that the amount of threads specified.  
+**Warning:** When using this mode, not checks will be done to ensure an array of objects exists in the data. So in some circumstances, if the wrong options are chosen, no error will be raised.  
 
 **Warning:** May have issues with inline-one-to-one as each thread will determine what should be inlined.