Compare commits

..
7 Commits
Author SHA1 Message Date
tech 105abf4e24 Update signed manifest to 7.23.38 2026-08-12 17:08:28 +00:00
tech d48beb9757 Update signed manifest to 7.23.37 2026-08-12 16:47:29 +00:00
tech 4a43572b15 Update signed manifest to 7.23.36 2026-08-12 15:43:51 +00:00
tech 20c46d3d26 Update signed manifest to 7.23.35 2026-08-12 15:40:08 +00:00
tech 74fdd42561 Update signed manifest to 7.23.34 2026-08-12 15:34:18 +00:00
tech 1e4806457e Update signed manifest to 7.23.33 2026-08-12 15:28:05 +00:00
tech da9237171a Update signed manifest to 7.23.32 2026-08-12 15:26:38 +00:00
+6 -6
View File
@@ -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.38",
"released_at": "2026-08-12T17:08:27+00:00",
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.23.38/argus-wordpress-defence-7.23.38.zip",
"sha256": "ca6d9a05d749f2483089bd2f6b9f58b322384f51a39c29fd90bb339c5bfc397f",
"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": "* Findings that ARGUS already handled automatically (a blocked WAF request, a blocked file\n upload, blocked REST user-enumeration probing) no longer sit in \"Needs Attention\" -- the same\n fix already shipped for brute-force login findings in 7.23.37 now covers every place this\n happened. Existing findings from before this fix are cleaned up automatically on update, not\n just new ones going forward.\n* The Protection Score on Overview is now color-coded (green/yellow/orange/red) instead of always\n the same color regardless of how healthy your site actually is.\n* Backup integrity is now fully automatic end to end -- no \"Verify\" button to click; ARGUS\n re-checks every backup's integrity once a day on its own, on top of the check it already does\n the moment a backup is created.\n* The Backups page now displays properly on a phone.\n* New \"Purge Audit Log\" option on the Audit Log page, for clearing it manually at any time.",
"signature": "y9yWsjrUnm9datO0rsvoQRudPDAtG3e7fpnCjuPNWr33nTsz1js9l0PXiCer7otHeaL6QyDSV+Q0j+R6xZBhCQ=="
}