| Release | When | Supported | Status |
|---|---|---|---|
| In service | |||
| 10.11.0 LTS | Since Mar 2024 | Until 14.0.0, Jul 2027 | For production |
| 9.24.0 | Since Jul 2020 | Until 11.0.0, Oct 2026 | One final release, then end of life |
| 8.19.0 | Since May 2018 | Until 11.0.0, Oct 2026 | One final release, then end of life |
| Scheduled | |||
| 11.0.0 | Oct 2026 | Until 12.0.0, Jan 2027 | Next up |
| 12.0.0 | Jan 2027 | Until 13.0.0, Apr 2027 | Scheduled |
| 10.12.0 LTS | Jan 2027 | Until 14.0.0, Jul 2027 | Scheduled |
| 13.0.0 | Apr 2027 | Until 14.0.0, Jul 2027 | Scheduled |
| 14.0.0 LTS | Jul 2027 | Until 18.0.0, Jul 2028 | Scheduled |
| Out of service | |||
If your application is not on a line in service, plan the upgrade: the upgrade paths show the route. Every release line links to its own page.
Upgrade paths
How to move an application to a line that stays supported.
| You are on | Your route | Guide |
|---|---|---|
| Wicket 8.x or 9.x |
8.x → 9 (Java 11) → 10 LTS (Java 17) → 14 LTS, July 2027 Both lines get one final release and reach end of life when Wicket 11.0.0 ships, and with them Wicket's support for |
Migration to Wicket 9 Migration to Wicket 10 |
| Wicket 10.x | Stay on the LTS until Wicket 14, the next LTS, ships in July 2027. Wicket 11, the first quarterly release, brings new features and needs Java 21 and Jakarta Servlet 6.1. | The new release cadence |
| Starting out | Start on 10 LTS. Once Wicket 11 is out, start on 11 instead if you want new features every quarter. | Create a project |
Release policy
With the release of Wicket 11.0.0, due in October 2026, Wicket moves to a time-based release schedule: a new major release every three months, and every fourth major release — once a year — is a long term support (LTS) release. The table above shows the lines as they are today and the releases scheduled after them.
From then on, two release lines are maintained at any time:
- the current LTS release, which receives security fixes and applicable bug fixes until the next LTS release;
- the current quarterly release, which receives fixes until the next quarterly release supersedes it. Fixes normally ride along with that next release; a serious issue may warrant a patch release, for example 13.0.1.
The support window applies to the release line, not to individual features. Features are
developed on main and carry over into every following release, so a feature introduced
in Wicket 11 is also present in 12, 13 and in the next LTS, Wicket 14.
Wicket 10 is the current LTS and stays supported until Wicket 14 is released in the first
week of July 2027. Wicket 8.x and 9.x each receive one final release and are then end of
life, and with them Wicket’s support for the javax.servlet API.
The full announcement is in our news archive: A new release cadence for Apache Wicket.
Unsupported releases
The following releases are no longer supported by the Wicket team. You should upgrade your project if it still depends on any of these versions.
| Version | Latest release | Status |
|---|---|---|
| Wicket 7.x | 7.18.0 | End of life upgrade to 10.x LTS |
| Wicket 6.x | 6.30.0 | End of life upgrade to 10.x LTS |
| Wicket 1.5.x | 1.5.16 | End of life upgrade to 10.x LTS |
| Wicket 1.4.x | 1.4.23 | End of life upgrade to 10.x LTS |
| Wicket 1.3.x | 1.3.7 | End of life upgrade to 10.x LTS |
| Wicket 1.2.x | 1.2.5 | End of life upgrade to 10.x LTS |
| Wicket 1.1.x | 1.1.0 | End of life upgrade to 10.x LTS |
| Wicket 1.0.x | 1.0.0 | End of life upgrade to 10.x LTS |
Release archives
The Apache mirroring system only hosts the latest version of each actively supported branch. When you need to download an older release you can find them in the archives.
Go to the Apache archives to find your specific version.
SNAPSHOT repository
In order to use any SNAPSHOT versions mentioned in each download section of a specific Wicket version you have to configure the SNAPSHOT repository in your pom.xml.
<repository>
<id>apache.snapshots</id>
<name>Apache Development Snapshot Repository</name>
<url>https://repository.apache.org/content/repositories/snapshots/</url>
<releases>
<enabled>false</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
</repository>Beware that SNAPSHOT versions might be deleted after a while and that you should not use any of them to go live with.