This is an automated email from the ASF dual-hosted git repository.
dashorst pushed a commit to branch wicket-10.x
in repository https://gitbox.apache.org/repos/asf/wicket.git
The following commit(s) were added to refs/heads/wicket-10.x by this push:
new 266b6b3abd Mark Wicket 9.x and 8.x as discontinued in the security
policy
266b6b3abd is described below
commit 266b6b3abd9b4288762f4168512a30f4aa05cbbf
Author: Martijn Dashorst <[email protected]>
AuthorDate: Fri Oct 30 00:24:07 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 and deprecation is
judged per line for 10.x alone. The link for the status of each line
points to the releases page; start/download.html only redirects there.
Generated-by: Claude Code (Claude Opus 5.5)
---
SECURITY.md | 10 ++++------
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git a/SECURITY.md b/SECURITY.md
index 84137b3b0f..7f7c799418 100644
--- a/SECURITY.md
+++ b/SECURITY.md
@@ -46,16 +46,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)
@@ -79,7 +77,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