Compare commits

...
11 Commits
Author SHA1 Message Date
tech 22b7a76a6e Update signed manifest to 7.73.0 2026-10-31 19:09:01 +00:00
tech 1544198d02 Update signed manifest to 7.72.0 2026-10-31 18:02:19 +00:00
tech 4b3e877127 Update signed manifest to 7.71.5 2026-10-31 15:26:33 +00:00
tech 8324647177 Update signed manifest to 7.71.4 2026-10-31 15:04:01 +00:00
tech eec9b0e6f0 Update signed manifest to 7.71.2 2026-10-22 07:41:09 +00:00
tech 301e39dc66 Update signed manifest to 7.71.1 2026-10-20 13:37:17 +00:00
tech aed69ceb6e Update signed manifest to 7.70.3 2026-10-20 08:00:48 +00:00
tech 82b525ca1e Update signed manifest to 7.70.2 2026-10-19 20:14:36 +00:00
tech 543bdd58d4 Update signed manifest to 7.70.1 2026-10-19 20:01:49 +00:00
tech 1ff0bdbeca Update signed manifest to 7.70.0 2026-10-19 14:01:51 +00:00
tech 09ac6a1fda Update signed manifest to 7.69.1 2026-10-19 13:49:44 +00:00
+6 -6
View File
@@ -1,11 +1,11 @@
{ {
"version": "7.69.0", "version": "7.73.0",
"released_at": "2026-10-19T13:37:38+00:00", "released_at": "2026-10-31T19:09:01+00:00",
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.69.0/argus-wordpress-defence-7.69.0.zip", "package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.73.0/argus-wordpress-defence-7.73.0.zip",
"sha256": "d1c006de4e32d83d929285c6768633a4c1f21067560bb9a2c24280021e0d9014", "sha256": "34877adbeda02cef2046bb7f088c937b6d3d9c16a87596dfe65bca8d08be9300",
"min_php": "7.4", "min_php": "7.4",
"min_wp": "6.0", "min_wp": "6.0",
"critical": true, "critical": true,
"summary": "* Fixed a blank page after using Archive, Resolve, Acknowledge and the other actions on a finding\n once you had switched tabs or pages in Findings. You now return to the same tab and page, and a\n refused action is shown as an error instead of a success message.\n* The same threat arriving from many different addresses is now challenged automatically, instead of\n staying \"allowed\" however many addresses it came from. The thresholds are unchanged.\n* The \"Needs Attention\" tab in Findings is now called \"Critical & High\", which is exactly what it\n shows. Medium and low findings stay under \"Active\".\n* If ARGUS cannot apply a block or challenge, you now see a single clear finding about it instead of\n nothing, and a challenge that cannot be issued no longer shows a page nobody can complete.\n* Finding descriptions now say how many different sources a threat came from, rather than implying\n every request came from the most recent address.\n* Findings about a threat that was only \"allowed\" before this fix are closed automatically on update, with their evidence kept, and re-open if the threat comes back unchallenged.", "summary": "* WordPress core upgrades through ARGUS now use a safe, recoverable process: ARGUS first checks\n that your site is ready for the upgrade, verifies compatibility, takes a validated recovery\n backup, performs the upgrade, and automatically rolls back if a critical problem is detected\n afterwards. The upgrade button now gives a clear explanation if the safe upgrade process is not\n yet enabled on a site, rather than failing silently.\n* The \"Check upgrade readiness\" option now works correctly -- it runs a full compatibility and\n risk analysis and shows a report without making any changes to your site.",
"signature": "T78BKVQ08ouM8bqvKryZ3AN8SxAY+sySZfdBeCJA6jlsJMZO7GrHsnyRnyQ/lh2AcEUXiz9AiHr/syIIe5CDDw==" "signature": "Jx2wWfhIZ0UgHekgjBeUH8hBczvbI8smv+nlelScfzgBKUPRTPULYR7q1CZXK6H/nOzncb19GaxnJ66ZbJJ5AQ=="
} }