Compare commits

...
3 Commits
Author SHA1 Message Date
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
+6 -6
View File
@@ -1,11 +1,11 @@
{ {
"version": "7.58.0", "version": "7.61.0",
"released_at": "2026-10-07T11:13:22+00:00", "released_at": "2026-10-07T20:54:25+00:00",
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.58.0/argus-wordpress-defence-7.58.0.zip", "package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.61.0/argus-wordpress-defence-7.61.0.zip",
"sha256": "b140d997084875edafa67a4762f3f7ec5662c17cbf9670a024b092351e950a90", "sha256": "9b9cc0630470344a04c3440888919a885b916a057bb19f9d3eae3ab49a8bbc53",
"min_php": "7.4", "min_php": "7.4",
"min_wp": "6.0", "min_wp": "6.0",
"critical": false, "critical": false,
"summary": "* Findings for events ARGUS already handled automatically -- a brute-force IP ban, a bad-bot\n auto-block -- now consistently say so, instead of occasionally still showing \"Nothing\n automatically\" after the action already happened.\n* If an automatic ban ever fails to save, ARGUS now raises its own finding about that failure\n instead of quietly treating the event as resolved.\n* Vulnerability Protection now recognises ARGUS WordPress Defence itself as a trusted, first-party\n component, instead of showing it as an unverified external plugin just because it isn't\n distributed through WordPress.org. A real vulnerability in ARGUS's own code is still detected\n and flagged just the same.", "summary": "* A new registration Form Protection holds for your review can now actually be approved or\n rejected, from a new \"Pending Registration Reviews\" list on the Form Protection page -- Approve\n just closes the review, Reject stops that one account logging in without deleting it. Neither\n action adds the address to any trusted or blocked list on its own.\n* Every entry in Form Activity now has its own \"Trust address\" and \"Block address\" buttons, so you\n no longer need to go to the Firewall page to act on an address you see there.\n* Form Activity now shows plainly what actually happens to a held submission: for comments and new\n registrations, it's genuinely held and waiting for you; for Contact Form 7, WPForms and Gravity\n Forms, \"held for review\" already meant the submission was delivered (with its notification\n suppressed where possible) -- that's now stated outright instead of implied.\n* A request to a generic WordPress API address (used by the block editor and other core features,\n not by any contact form) no longer shows up in Form Activity labeled as a form submission.\n* When \"keep a short excerpt of the raw submission\" is switched on, that excerpt is now actually\n shown next to the matching entry in Form Activity -- and is automatically and permanently removed\n after a retention period you choose (24 hours, 72 hours, or 7 days), independently of how long the\n rest of your activity log is kept.",
"signature": "1DvPQAaVW591I8ZNfz4ZVl0xTsJOOzRy1NCcrl3k6vizqbsrG4kvJd3O5lDLD23Q5VsFrUlM5BT/vatxN7soDQ==" "signature": "cu5hJpT2hEHpqTHjD/ChLGdUV16tNv8D/17pc29dDNNy8Y6TholeZF/Gb71ARZ5GRVp3ZFJJNoYOdcSP57tADg=="
} }