EOL.Wiki EOL.Wiki
← ← Back to all products

Quarkus

Active
Frameworks Latest Version: 3.36.2 Latest Release: Jun 11, 2026

Quarkus is a Kubernetes-native Java framework tailored for GraalVM and OpenJDK, optimized for containers.

Versions

56

Latest Version

3.36.2

Active Support

3

EOL

53

Lifecycle Timeline

Today
3.36
3.36
3.35
3.35
3.34
3.34
3.33
3.33
3.32
3.32
3.31
3.31
3.30
3.30
3.29
3.29
3.28
3.28
3.27
3.27
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
3.36May 27, 2026YesNo3.36.2No
Active
3.35May 1, 2026NoMay 27, 20263.35.4No
EOL
3.34Mar 25, 2026NoMay 1, 20263.34.7No
EOL
3.33Mar 25, 2026YesMar 25, 20273.33.2
Yes
Active
3.32Feb 26, 2026NoMar 25, 20263.32.4No
EOL
3.31Jan 28, 2026NoFeb 26, 20263.31.4No
EOL
3.30Nov 26, 2025NoJan 28, 20263.30.8No
EOL
3.29Oct 29, 2025NoNov 26, 20253.29.4No
EOL
3.28Sep 24, 2025NoOct 29, 20253.28.5No
EOL
3.27Sep 24, 2025YesSep 24, 20263.27.4
Yes
Active
3.26Aug 28, 2025NoSep 24, 20253.26.4No
EOL
3.25Jul 30, 2025NoAug 28, 20253.25.4No
EOL
3.24Jun 25, 2025NoJul 30, 20253.24.5No
EOL
3.23May 28, 2025NoJun 25, 20253.23.4No
EOL
3.22Apr 30, 2025NoMay 28, 20253.22.3No
EOL
3.21Mar 26, 2025NoApr 30, 20253.21.4No
EOL
3.20Mar 26, 2025NoMar 28, 20263.20.6.1
Yes
EOL
3.19Feb 26, 2025NoMar 28, 20253.19.4No
EOL
3.18Jan 29, 2025NoFeb 26, 20253.18.4No
EOL
3.17Nov 27, 2024NoJan 29, 20253.17.8No
EOL
3.16Oct 30, 2024NoNov 27, 20243.16.4No
EOL
3.15Sep 25, 2024NoSep 25, 20253.15.7
Yes
EOL
3.14Aug 28, 2024NoSep 25, 20243.14.4No
EOL
3.13Jul 31, 2024NoAug 28, 20243.13.3No
EOL
3.12Jun 26, 2024NoJul 31, 20243.12.3No
EOL
3.11May 29, 2024NoJun 26, 20243.11.3No
EOL
3.10Apr 30, 2024NoMay 29, 20243.10.2No
EOL
3.9Mar 27, 2024NoApr 30, 20243.9.5No
EOL
3.8Feb 28, 2024NoFeb 28, 20253.8.6.1
Yes
EOL
3.7Jan 31, 2024NoFeb 28, 20243.7.4No
EOL
3.6Nov 29, 2023NoJan 31, 20243.6.9No
EOL
3.5Oct 25, 2023NoNov 29, 20233.5.3No
EOL
3.4Sep 20, 2023NoOct 25, 20233.4.3No
EOL
3.3Aug 23, 2023NoSep 20, 20233.3.3No
EOL
3.2Jul 5, 2023NoJul 5, 20243.2.12
Yes
EOL
3.1May 31, 2023NoJul 5, 20233.1.3No
EOL
3.0Apr 26, 2023NoMay 31, 20233.0.4No
EOL
2.16Jan 25, 2023NoOct 31, 20232.16.12No
EOL
2.15Dec 14, 2022NoJan 25, 20232.15.3No
EOL
2.14Nov 9, 2022NoDec 14, 20222.14.3No
EOL
2.13Sep 28, 2022NoNov 7, 20222.13.9No
EOL
2.12Aug 31, 2022NoSep 21, 20222.12.3No
EOL
2.11Jul 27, 2022NoAug 24, 20222.11.3No
EOL
2.10Jun 22, 2022NoJul 26, 20222.10.4No
EOL
2.9May 11, 2022NoJun 15, 20222.9.2No
EOL
2.8Apr 12, 2022NoMay 6, 20222.8.3No
EOL
2.7Feb 2, 2022NoMay 30, 20222.7.7No
EOL
2.6Dec 22, 2021NoJan 26, 20222.6.3No
EOL
2.5Nov 24, 2021NoDec 17, 20212.5.4No
EOL
2.4Oct 27, 2021NoNov 17, 20212.4.2No
EOL
2.3Oct 6, 2021NoOct 20, 20212.3.1No
EOL
2.2Aug 31, 2021NoDec 21, 20212.2.5No
EOL
2.1Jul 29, 2021NoAug 26, 20212.1.4No
EOL
2.0Jun 30, 2021NoJul 22, 20212.0.3No
EOL
1Nov 25, 2019NoJun 23, 20211.13.7No
EOL
0Dec 12, 2018NoNov 25, 20190.28.1No
EOL

Frequently Asked Questions

Which versions of Quarkus have reached end of life?
The following Quarkus versions have reached end of life and no longer receive security updates: 3.35, 3.34, 3.32, 3.31, 3.30, 3.29, 3.28, 3.26 (and 45 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Quarkus 3.35?
Quarkus 3.35 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 Quarkus?
The latest version of Quarkus is 3.36.2, released in the 3.36 release cycle.
How many versions of Quarkus are currently supported?
Quarkus currently has 3 actively supported version(s): 3.36, 3.33, 3.27.
When does Quarkus 3.36 reach end of life?
Quarkus 3.36 does not have a specific end-of-life date announced yet.
What should I do when Quarkus reaches end of life?
When a Quarkus 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.