Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
22b7a76a6e | ||
|
|
1544198d02 | ||
|
|
4b3e877127 | ||
|
|
8324647177 | ||
|
|
eec9b0e6f0 | ||
|
|
301e39dc66 | ||
|
|
aed69ceb6e | ||
|
|
82b525ca1e | ||
|
|
543bdd58d4 | ||
|
|
1ff0bdbeca | ||
|
|
09ac6a1fda | ||
|
|
2ce45b9c2d | ||
|
|
21ed592b8b | ||
|
|
cc56098488 | ||
|
|
8fa6153099 | ||
|
|
c8f8640e4c | ||
|
|
50336dfd90 | ||
|
|
85997bca02 |
+7
-7
@@ -1,11 +1,11 @@
|
|||||||
{
|
{
|
||||||
"version": "7.62.0",
|
"version": "7.73.0",
|
||||||
"released_at": "2026-10-07T21:41:57+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.62.0/argus-wordpress-defence-7.62.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": "67965da074b92518297d7da22a24f4d954ae03ecea3be948b235dc4ab60ded5c",
|
"sha256": "34877adbeda02cef2046bb7f088c937b6d3d9c16a87596dfe65bca8d08be9300",
|
||||||
"min_php": "7.4",
|
"min_php": "7.4",
|
||||||
"min_wp": "6.0",
|
"min_wp": "6.0",
|
||||||
"critical": false,
|
"critical": true,
|
||||||
"summary": "* Monitor Mode no longer creates a separate finding for every bot signature or attacking IP it\n observes -- they now roll up into a single \"ARGUS is in Monitor Mode\" finding, so switching to\n Block Mode is one decision instead of dozens.\n* In Monitor Mode, a detected credential-stuffing attempt is no longer banned behind the scenes --\n like every other Monitor Mode detection, it is now only observed and counted in the Monitor Mode\n finding above, until you switch to Block Mode.",
|
"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": "6/F/eRCZAaf1dJeNSBHeXNVXY9HHlXqUnt0l7CmML19iJtwOAtOg0zJcPqJDoXOsuzNrqyQX3+xPJbzpq6AIAg=="
|
"signature": "Jx2wWfhIZ0UgHekgjBeUH8hBczvbI8smv+nlelScfzgBKUPRTPULYR7q1CZXK6H/nOzncb19GaxnJ66ZbJJ5AQ=="
|
||||||
}
|
}
|
||||||
|
|||||||
Reference in New Issue
Block a user