Update signed manifest to 7.64.0

This commit is contained in:
2026-10-08 07:51:54 +00:00
parent 85997bca02
commit 50336dfd90
+6 -6
View File
@@ -1,11 +1,11 @@
{ {
"version": "7.63.0", "version": "7.64.0",
"released_at": "2026-10-08T06:48:51+00:00", "released_at": "2026-10-08T07:51:53+00:00",
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.63.0/argus-wordpress-defence-7.63.0.zip", "package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.64.0/argus-wordpress-defence-7.64.0.zip",
"sha256": "4185f4d090d6edaafe86952c017bc60b7673dd4b39402740872e1b8167a1abbb", "sha256": "61cfa4d5f06e158f4c45233393bbb428c17877111cdc44f8858f0ea210889eea",
"min_php": "7.4", "min_php": "7.4",
"min_wp": "6.0", "min_wp": "6.0",
"critical": false, "critical": false,
"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.", "summary": "* Closed a narrower follow-up gap in 7.63.0: an IP that was banned shortly after some failed login\n attempts could still get a duplicate \"suspicious behavior\" finding, because the failed attempts\n that led to the ban were being counted as separate new evidence. A genuinely unresolved attempt\n that never actually got banned is unaffected and still shows up for your review, as before.",
"signature": "PWMBZPER9IETw5Vjdvdly578k5fTmd8BQDCMFdejYQJhd8ShkOmni/hmXVQQ4ap6LAiXhXJd7gfkFincqq08Aw==" "signature": "4OnNOph3V6legWOe/rdi9c3LUANDxKrAvSFg/OKAt3lkRK/zP1Ev7IU2BhqwbBUshmT/0osmzo4k7AluTXdCCA=="
} }