Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
22b7a76a6e | ||
|
|
1544198d02 | ||
|
|
4b3e877127 | ||
|
|
8324647177 | ||
|
|
eec9b0e6f0 | ||
|
|
301e39dc66 | ||
|
|
aed69ceb6e | ||
|
|
82b525ca1e | ||
|
|
543bdd58d4 | ||
|
|
1ff0bdbeca | ||
|
|
09ac6a1fda | ||
|
|
2ce45b9c2d | ||
|
|
21ed592b8b | ||
|
|
cc56098488 | ||
|
|
8fa6153099 | ||
|
|
c8f8640e4c | ||
|
|
50336dfd90 | ||
|
|
85997bca02 | ||
|
|
3aa96c7b3e | ||
|
|
a8108f9b84 | ||
|
|
d89b0d09a9 |
+6
-6
@@ -1,11 +1,11 @@
|
||||
{
|
||||
"version": "7.59.0",
|
||||
"released_at": "2026-10-07T15:31:32+00:00",
|
||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.59.0/argus-wordpress-defence-7.59.0.zip",
|
||||
"sha256": "f9ba43c57d969b71ddd763151a6a2c97a79a9971635deeca57f23c7221b3ee29",
|
||||
"version": "7.73.0",
|
||||
"released_at": "2026-10-31T19:09:01+00:00",
|
||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.73.0/argus-wordpress-defence-7.73.0.zip",
|
||||
"sha256": "34877adbeda02cef2046bb7f088c937b6d3d9c16a87596dfe65bca8d08be9300",
|
||||
"min_php": "7.4",
|
||||
"min_wp": "6.0",
|
||||
"critical": true,
|
||||
"summary": "* A file-integrity finding that was correct when first detected could keep showing as a critical,\n unresolved problem even after a later official ARGUS Defence update made the file match the\n real, signed release again. These findings now re-check themselves against the version you\n actually have installed and clear automatically once that's confirmed -- a genuinely tampered\n file still shows as critical, backed by a fresh check, not a stale one.",
|
||||
"signature": "tvH0duWx7DbAGMkE1o/54nt6CybrvQCLfWby8fWUtc1tY8ZteJpu40ekDIOf2rbM4qq0VpeILbKbYvyw/HRCDQ=="
|
||||
"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": "Jx2wWfhIZ0UgHekgjBeUH8hBczvbI8smv+nlelScfzgBKUPRTPULYR7q1CZXK6H/nOzncb19GaxnJ66ZbJJ5AQ=="
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user