Releases¶
Versions¶
Below is a non-exhaustive list of versions and their maintenance status:
| Version | Release Date | Active Support | Security Support |
|---|---|---|---|
| 3.7 | May 05, 2026 | Yes | Yes |
| 3.6 | Nov 07, 2025 | Ended May 07, 2026 | Ends Aug 16, 2026 |
| 3.5 | Jul 23, 2025 | Ended Nov 07, 2025 | No |
| 3.4 | May 05, 2025 | Ended Jul 23, 2025 | No |
| 3.3 | Jan 06, 2025 | Ended May 05, 2025 | No |
| 3.2 | Oct 28, 2024 | Ended Jan 06, 2025 | No |
| 3.1 | Jul 15, 2024 | Ended Oct 28, 2024 | No |
| 3.0 | Apr 29, 2024 | Ended Jul 15, 2024 | No |
| 2.11 | Feb 12, 2024 | Ended Apr 29, 2025 | Ended Feb 01, 2026 |
Active Support / Security Support
-
Active support: Receives any bug fixes.
-
Security support: Receives only critical bug and security fixes.
This page is maintained and updated periodically to reflect our roadmap and any decisions affecting the end of support for Traefik Proxy.
Please refer to our migration guides for specific instructions on upgrading between versions, an example is the v2 to v3 migration guide.
All target dates for end of support or feature removal announcements may be subject to change.
Versioning Scheme¶
The Traefik Proxy project follows the semantic versioning scheme and maintains a separate branch for each minor version. The main branch always represents the next upcoming minor or major version.
And these are our guiding rules for version support, as of Traefik v3.6:
- Every
minoris supported for 6 months from its GA release date, which means severalminorversions can be supported at the same time - The last
minorafter releasing a newmajoris supported for 2 years following themajorrelease (starting with v3) - Previous rules are subject to change and in such cases an announcement will be made publicly, here is an example extending v1.x branch support.
Versions released before v3.6
These rules apply starting with Traefik v3.6. Before that, only the latest minor was on active support at any given time, and support for a minor ended as soon as the next one was released.