diff --git a/manifest.json b/manifest.json
index acb4478..923a08c 100644
--- a/manifest.json
+++ b/manifest.json
@@ -1,11 +1,11 @@
 {
-    "version": "7.23.31",
-    "released_at": "2026-08-12T15:21:11+00:00",
-    "package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.23.31/argus-wordpress-defence-7.23.31.zip",
-    "sha256": "32bc52ca330a96ea39ea645845687bb49aceaf9fda37ec5362254d5255fcc059",
+    "version": "7.23.32",
+    "released_at": "2026-08-12T15:26:37+00:00",
+    "package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.23.32/argus-wordpress-defence-7.23.32.zip",
+    "sha256": "6439eb8b52c3ffec514d73705ea57aa461fcfe2e781bd0c298688697ed0ee2ea",
     "min_php": "7.4",
     "min_wp": "6.0",
     "critical": false,
-    "summary": "* Fixed: right after ARGUS checked for updates, its own health check could momentarily read that\n  timestamp before it was refreshed and report \"hasn't checked for updates\" -- the two checks now\n  run in the correct order.\n* The health-check findings for scanner/update/intelligence timing now explain the most common\n  real cause specifically -- WordPress's own scheduled-task system (WP-Cron) not firing reliably,\n  common on low-traffic sites or hosts without a real system cron configured -- instead of a\n  generic \"contact support.\"",
-    "signature": "OzT7amiVmnb2viT+xAnMIfepOYPag5V9F34qNcxtd8Vw6qd0OE9cO8D5iCQn8wXE7jRUKloxq7/UI+Y5LW14Dw=="
+    "summary": "* Fixed a real bug found on a live production site right after 7.23.31 shipped: the new\n  self-health-check for the scanner and the update mechanism compared timestamps in the wrong\n  format, so it could report \"hasn't run in hours\" / \"hasn't checked in 2 days\" even seconds after\n  they genuinely had. Both are now correctly recognized as healthy when they actually are.",
+    "signature": "XnGoKDoybXWln+XMgRVSYJM+0VMsvXRvJfnoDTf0bCvkLdX5a+Enq2jIMrMouDCrHmp7qp76/0P2tRmA0PidDA=="
 }