Compare commits

..
26 Commits
Author SHA1 Message Date
tech 2ce45b9c2d Update signed manifest to 7.69.0 2026-10-19 13:37:39 +00:00
tech 21ed592b8b Update signed manifest to 7.68.0 2026-10-19 08:50:53 +00:00
tech cc56098488 Update signed manifest to 7.67.0 2026-10-18 12:43:00 +00:00
tech 8fa6153099 Update signed manifest to 7.66.0 2026-10-15 14:06:22 +00:00
tech c8f8640e4c Update signed manifest to 7.65.0 2026-10-09 10:02:58 +00:00
tech 50336dfd90 Update signed manifest to 7.64.0 2026-10-08 07:51:54 +00:00
tech 85997bca02 Update signed manifest to 7.63.0 2026-10-08 06:48:52 +00:00
tech 3aa96c7b3e Update signed manifest to 7.62.0 2026-10-07 21:41:58 +00:00
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
tech 68cc299d16 Update signed manifest to 7.58.0 2026-10-07 11:13:23 +00:00
tech 5657d78e13 Update signed manifest to 7.57.0 2026-10-07 09:48:13 +00:00
tech 0fb24b0e7b Update signed manifest to 7.56.0 2026-10-06 12:36:24 +00:00
tech 19957d44b0 Update signed manifest to 7.55.0 2026-10-05 22:43:45 +00:00
tech 4054510acc Update signed manifest to 7.54.0 2026-10-05 17:12:23 +00:00
tech a0885f319a Update signed manifest to 7.53.0 2026-09-25 09:30:08 +00:00
tech a8cdbef65a Update signed manifest to 7.52.0 2026-09-23 09:51:35 +00:00
tech 806094d6a0 Update signed manifest to 7.51.0 2026-09-19 16:44:44 +00:00
tech 0faf78287a Update signed manifest to 7.49.0 2026-09-19 10:22:45 +00:00
tech 235169e8ac Update signed manifest to 7.46.0 2026-09-17 23:20:51 +00:00
tech 67323f0204 Update signed manifest to 7.45.5 2026-09-17 22:40:55 +00:00
tech f3a00c618b Update signed manifest to 7.45.4 2026-09-17 22:28:23 +00:00
tech d39aa6f9bc Update signed manifest to 7.45.1 2026-09-17 18:11:59 +00:00
tech efb0dfc838 Update signed manifest to 7.45.0 2026-09-17 17:48:05 +00:00
tech 7fa580d4d6 Update signed manifest to 7.44.0 2026-09-17 16:36:26 +00:00
+7 -7
View File
@@ -1,11 +1,11 @@
{ {
"version": "7.43.0", "version": "7.69.0",
"released_at": "2026-09-17T12:33:02+00:00", "released_at": "2026-10-19T13:37:38+00:00",
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.43.0/argus-wordpress-defence-7.43.0.zip", "package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.69.0/argus-wordpress-defence-7.69.0.zip",
"sha256": "cdc118a3fc386a38b376c089bcbb4276a6f6a9cbaa847eb2586320553d4c621d", "sha256": "d1c006de4e32d83d929285c6768633a4c1f21067560bb9a2c24280021e0d9014",
"min_php": "7.4", "min_php": "7.4",
"min_wp": "6.0", "min_wp": "6.0",
"critical": false, "critical": true,
"summary": "* ARGUS's own automatic updates no longer create a flood of integrity findings for the files that\n update legitimately changed -- each one is now checked against that exact release's own signed\n file list, so a genuine ARGUS update stays quiet while anything unexpected (a file that update\n did not actually add, or one it removed but this version still needs) is still caught and\n reported, not silently ignored.", "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.",
"signature": "aS+aCokuI9o+k8CkM9NbifEWrOq+iz1wcRFkiWDIR2T9rGF+Xd47TIJDjKoyS3Ll2nx65uBobTCyr3mlK18KAQ==" "signature": "T78BKVQ08ouM8bqvKryZ3AN8SxAY+sySZfdBeCJA6jlsJMZO7GrHsnyRnyQ/lh2AcEUXiz9AiHr/syIIe5CDDw=="
} }