Compare commits

...
7 Commits
Author SHA1 Message Date
tech 85997bca02 Update signed manifest to 7.63.0 2026-10-08 06:48:52 +00:00
tech 3aa96c7b3e Update signed manifest to 7.62.0 2026-10-07 21:41:58 +00:00
tech a8108f9b84 Update signed manifest to 7.61.0 2026-10-07 20:54:26 +00:00
tech d89b0d09a9 Update signed manifest to 7.60.0 2026-10-07 20:29:14 +00:00
tech fa1beeb71d Update signed manifest to 7.59.0 2026-10-07 15:31:33 +00:00
tech 68cc299d16 Update signed manifest to 7.58.0 2026-10-07 11:13:23 +00:00
tech 5657d78e13 Update signed manifest to 7.57.0 2026-10-07 09:48:13 +00:00
+6 -6
View File
@@ -1,11 +1,11 @@
{ {
"version": "7.56.0", "version": "7.63.0",
"released_at": "2026-10-06T12:36:23+00:00", "released_at": "2026-10-08T06:48:51+00:00",
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.56.0/argus-wordpress-defence-7.56.0.zip", "package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.63.0/argus-wordpress-defence-7.63.0.zip",
"sha256": "c6a8bb73b91943e69bde39d7ebce5d1ea9670f20e13824f99dd8dd74c9052906", "sha256": "4185f4d090d6edaafe86952c017bc60b7673dd4b39402740872e1b8167a1abbb",
"min_php": "7.4", "min_php": "7.4",
"min_wp": "6.0", "min_wp": "6.0",
"critical": false, "critical": false,
"summary": "* Every finding now clearly states whether ARGUS already took action and exactly what it did,\n instead of folding that into the general advice text.\n* A file ARGUS automatically quarantines now shows its own distinct status until you decide\n whether to restore or permanently delete it, instead of looking identical to an untouched,\n unreviewed finding.\n* Correlation-based findings now explain what was found in plain language.\n* Form Protection can now recognise business-inquiry submissions with inconsistent details --\n for example a personal email address on a form that asked for a company name, an email that\n doesn't match the stated company, or a generic, templated-sounding message -- and raises them\n for your review instead of letting them through unnoticed.", "summary": "* Fixed a real gap in the 7.62.0 Monitor Mode fix: a bot ban or other already-fully-handled event\n could still turn into a second, separate \"suspicious behavior\" finding through Threat\n Correlation, duplicating what the Monitor Mode rollup (or the ban itself) had already covered.\n This no longer happens -- genuinely correlated, multi-signal findings are completely unaffected.",
"signature": "f+9T5Dzv/M0RwXtiEi9K6haHUxgVwwyyGAeEmkPqc7LqDocuSVQMXfuggtjprc3HTpc3TRxuNjUP+uFao9pfDg==" "signature": "PWMBZPER9IETw5Vjdvdly578k5fTmd8BQDCMFdejYQJhd8ShkOmni/hmXVQQ4ap6LAiXhXJd7gfkFincqq08Aw=="
} }