This is an automated email from the ASF dual-hosted git repository.

dashorst pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/wicket.git


The following commit(s) were added to refs/heads/master by this push:
     new 75ba768b6a Mark Wicket 9.x and 8.x as discontinued in the security 
policy
75ba768b6a is described below

commit 75ba768b6ad74360375ef951ce05378f376df96f
Author: Martijn Dashorst <[email protected]>
AuthorDate: Fri Oct 30 00:18:39 2026 +0100

    Mark Wicket 9.x and 8.x as discontinued in the security policy
    
    Wicket 9.25.0 and 8.20.0, released on 29 October 2026, were the final
    releases of both lines, so they no longer receive security fixes. The
    version table folds them into the discontinued row, a finding is
    verified against wicket-10.x or master only, deprecation is judged per
    line for 10.x alone, and the paragraph on 8.x lacking a resource
    isolation implementation goes, since all of 8.x is now out of scope.
    
    The link for the status of each line points to the releases page;
    start/download.html only redirects there. AGENTS.md names wicket-10.x
    as the one maintained release line.
    
    Generated-by: Claude Code (Claude Opus 5.5)
---
 AGENTS.md   |  4 ++--
 SECURITY.md | 24 +++++-------------------
 2 files changed, 7 insertions(+), 21 deletions(-)

diff --git a/AGENTS.md b/AGENTS.md
index 6ac2e73d59..bb5bc820c7 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -1,8 +1,8 @@
 # Apache Wicket
 
 Component-based Java web framework. `master` is the 11.x development line; the 
maintained
-release lines live on `wicket-10.x`, `wicket-9.x` and `wicket-8.x`. 
`SECURITY.md` says which of
-them still receive fixes.
+release line lives on `wicket-10.x`. `wicket-9.x` and `wicket-8.x` reached end 
of life with
+9.25.0 and 8.20.0. `SECURITY.md` says which lines still receive fixes.
 
 Versions — the Java release, the Servlet level, library and plugin versions — 
are not repeated
 here, because they go stale and then mislead. Read them from `pom.xml`.
diff --git a/SECURITY.md b/SECURITY.md
index 3b397a139d..4686868d9e 100644
--- a/SECURITY.md
+++ b/SECURITY.md
@@ -48,16 +48,14 @@ needs fixing.
 ## Supported Versions
 
 Security fixes are applied to the actively maintained release lines. Refer to
-the [download page](https://wicket.apache.org/start/download.html) for the
-current status and the latest release of each line.
+the [releases page](https://wicket.apache.org/versions/) for the current status
+and the latest release of each line.
 
 | Version | Status                                          |
 | ------- | ----------------------------------------------- |
 | 11.x    | In development (`master`) — not yet released     |
 | 10.x    | Current, supported                              |
-| 9.x     | Supported                                       |
-| 8.x     | Security fixes only — upgrade to 9.x or 10.x    |
-| ≤ 7.x   | Discontinued — no security fixes                |
+| ≤ 9.x   | Discontinued — no security fixes                |
 
 If you are running a discontinued version, the fix is to upgrade. See the
 [Migration to Wicket 
10.0](https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+10.0)
@@ -81,7 +79,7 @@ code is not fixed.
 Two limits on that, both of which cut in the reporter's favour:
 
 - **Deprecation is per release line.** A member deprecated on `master` may 
still
-  be current in 10.x or 9.x. A report is judged against the line it targets, 
not
+  be current in 10.x. A report is judged against the line it targets, not
   against `master`.
 - **Deprecating a member does not deprecate the behaviour behind it.** Where a
   deprecated accessor merely fronts a feature that is still current and still
@@ -155,18 +153,6 @@ report showing that a request *with* `Sec-Fetch-Site` 
present is nonetheless
 decided by the origin policy is in scope, as is anything else in
 `ResourceIsolationRequestCycleListener` itself.
 
-**8.x has no supported resource isolation implementation.** The
-`IResourceIsolationPolicy` mechanism arrived in 9.1.0. On 8.x the only
-cross-origin check Wicket offers is `CsrfPreventionRequestCycleListener`, which
-reads the same two headers with the same limits; 9.x deprecates it in favour of
-the resource isolation listener and it is therefore already out of scope there
-under [Deprecated code is out of scope](#deprecated-code-is-out-of-scope), 
while
-on 8.x it is not deprecated only because that line has nothing to migrate to. 
An
-8.x application that needs anything stronger has to upgrade or implement the 
check
-itself: we will not backport the fetch-metadata policy, and reports against
-`CsrfPreventionRequestCycleListener` are out of scope on the same footing as 
the
-origin policy.
-
 ### `wicket-examples` is sample code, not production code
 
 `wicket-examples` exists to demonstrate framework features in as few lines as
@@ -216,7 +202,7 @@ that can, and neither is a judgement on whether the concern 
behind it is real.
 ### A finding must be verified against a supported branch tip
 
 Verify the issue against the current tip of the line you are reporting against:
-`wicket-8.x`, `wicket-9.x`, `wicket-10.x`, or `master`. One of them is enough —
+`wicket-10.x` or `master`. One of them is enough —
 say which, and name the commit you tested. A failing test against that commit 
is
 ideal. Reporting only the release you happen to be running is not sufficient: a
 released artifact is always behind its branch, and what you found may already 
be

Reply via email to