The HAProxy development team takes a great care of maintaining stable versions so that all users can apply bug fixes without having to take the risk of upgrading to a new branch. In turn users are expected to apply the fixes when the development team estimates that they were worth being backported to stable branches. In short, if you are running any 3.2 version other than 3.2.22, you're running with known bugs.
| Date | Version | Comment |
|---|---|---|
| 2026-07-29 | 3.2.22 | ⇐ last |
| 2026-07-03 | 3.2.21 | |
| 2026-06-26 | 3.2.20 | |
| 2026-05-11 | 3.2.19 | |
| 2026-05-06 | 3.2.18 | |
| 2026-04-30 | 3.2.17 | |
| 2026-04-23 | 3.2.16 | |
| 2026-03-19 | 3.2.15 | |
| 2026-03-09 | 3.2.14 | |
| 2026-02-19 | 3.2.13 | |
| 2026-02-12 | 3.2.12 | |
| 2026-01-29 | 3.2.11 | |
| 2025-12-18 | 3.2.10 | |
| 2025-11-21 | 3.2.9 | |
| 2025-11-07 | 3.2.8 | |
| 2025-10-23 | 3.2.7 | |
| 2025-10-03 | 3.2.6 | |
| 2025-09-23 | 3.2.5 | |
| 2025-08-13 | 3.2.4 | |
| 2025-07-09 | 3.2.3 | |
| 2025-07-02 | 3.2.2 | |
| 2025-06-11 | 3.2.1 | |
| 2025-05-28 | 3.2.0 |
Bugs are almost always tagged with a severity (some people forget the severity tag when the bug is minor). The following severities are used :
Total known bugs in the latest version of this branch by category :
| Total | CRITICAL | MAJOR | MEDIUM | MINOR |
|---|---|---|---|---|
| 0 | 0 | 0 | 0 | 0 |
Click on the subjects below to get the full description of the bug :
| Merge date | Subject - Severity (minor, medium, major, critical) |
|---|
Back to the list of branches and versions
Back to the HAProxy page