diff --git a/challenger/pom.xml b/challenger/pom.xml
index 93195f1d..d25de871 100644
--- a/challenger/pom.xml
+++ b/challenger/pom.xml
@@ -10,7 +10,7 @@
     <modelVersion>4.0.0</modelVersion>
 
     <artifactId>challenger</artifactId>
-    <version>1.0.1</version>
+    <version>1.0.2</version>
 
     <dependencies>
         <dependency>
diff --git a/challengerAuto/pom.xml b/challengerAuto/pom.xml
index e2a40a03..4a0ca84d 100644
--- a/challengerAuto/pom.xml
+++ b/challengerAuto/pom.xml
@@ -20,7 +20,7 @@
         <dependency>
             <groupId>uk.co.compendiumdev.thingifier</groupId>
             <artifactId>challenger</artifactId>
-            <version>1.0.1</version>
+            <version>1.0.2</version>
             <scope>test</scope>
         </dependency>
 
diff --git a/pom.xml b/pom.xml
index 429b713c..f19b9cdc 100644
--- a/pom.xml
+++ b/pom.xml
@@ -9,7 +9,7 @@
 
 
     <properties>
-        <thingifier.version>1.5.5-SNAPSHOT</thingifier.version>
+        <thingifier.version>1.5.5</thingifier.version>
         <swagger-models-version>2.1.4</swagger-models-version>
         <gson-version>2.8.6</gson-version>
         <junit.jupiter.version>5.6.2</junit.jupiter.version>
@@ -48,6 +48,7 @@ Challenger
     - this mainly only affected the 'secret' token session because challenger was loaded during persistence of 'passing' a challenge
 - fixed defect where, when no Challenger X-CHALLENGER header on /secret the 401 response did not return, and so passed through into null pointer processing
 - surface any aws issues in the message headers and on GUI
+- added some additional challenges, sectioned and ordered
 
 1.5.4