← ← Back to all products
Jhipster
Active
Tools & Monitoring Latest Version: 9.0.0 Latest Release: Mar 11, 2026
JHipster is a development platform for generating Spring Boot + Angular/React/Vue web applications.
Versions
10
Latest Version
9.0.0
Active Support
1
EOL
9
Lifecycle Timeline
Today ↓
9
9
8
8
7
7
6
6
5
5
4
4
3
3
2
2
1
1
0
0
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 9 | Mar 11, 2026 | - | No | 9.0.0 | No | Active |
| 8 | Nov 2, 2023 | - | Mar 11, 2026 | 8.11.0 | No | EOL |
| 7 | Mar 21, 2021 | - | Nov 2, 2023 | 7.9.4 | No | EOL |
| 6 | May 2, 2019 | - | Mar 21, 2021 | 6.10.5 | No | EOL |
| 5 | Jun 20, 2018 | - | May 2, 2019 | 5.8.2 | No | EOL |
| 4 | Feb 2, 2017 | - | Jun 20, 2018 | 4.14.5 | No | EOL |
| 3 | Mar 23, 2016 | - | Feb 2, 2017 | 3.12.2 | No | EOL |
| 2 | Jan 12, 2015 | - | Mar 23, 2016 | 2.27.2 | No | EOL |
| 1 | Sep 1, 2014 | - | Jan 9, 2015 | 1.10.2 | No | EOL |
| 0 | Oct 21, 2013 | - | Sep 1, 2014 | 0.18.1 | No | EOL |
Frequently Asked Questions
Which versions of Jhipster have reached end of life?
The following Jhipster versions have reached end of life and no longer receive security updates: 8, 7, 6, 5, 4, 3, 2, 1 (and 1 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Jhipster 8?
Jhipster 8 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Jhipster?
The latest version of Jhipster is 9.0.0, released in the 9 release cycle.
How many versions of Jhipster are currently supported?
Jhipster currently has 1 actively supported version(s): 9.
When does Jhipster 9 reach end of life?
Jhipster 9 does not have a specific end-of-life date announced yet.
What should I do when Jhipster reaches end of life?
When a Jhipster version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.