diff --git a/package.json b/package.json
index c18fad53b1..705be39e86 100644
--- a/package.json
+++ b/package.json
@@ -96,7 +96,7 @@
     "ghost-storage-base": "0.0.4",
     "glob": "7.1.6",
     "got": "9.6.0",
-    "gscan": "4.0.0-pre.4",
+    "gscan": "4.0.0-pre.5",
     "html-to-text": "5.1.1",
     "image-size": "0.8.3",
     "intl": "1.2.5",
diff --git a/test/utils/fixtures/themes/README.md b/test/utils/fixtures/themes/README.md
index 06c36f614d..da2f6f3ab2 100644
--- a/test/utils/fixtures/themes/README.md
+++ b/test/utils/fixtures/themes/README.md
@@ -3,7 +3,7 @@ When a new rule is introduced in gscan one of these fixture files might break an
 
 - Unzip the theme files, e.g.: `cd $CURRENT_DIR && unzip valid.zip -d valid`
 - Make a change in the file which caused a warning/error/whatever
-- Zip the files back: ``
+- Zip the files back: `zip -r valid.zip ./valid`
 - Commit changed zip file: `git add valid.zip ;... you know the drill :)`
 
 Ideas for future improvements in theme tests:
diff --git a/test/utils/fixtures/themes/valid.zip b/test/utils/fixtures/themes/valid.zip
index ec6a69ec0e..cec79c9e9c 100644
Binary files a/test/utils/fixtures/themes/valid.zip and b/test/utils/fixtures/themes/valid.zip differ