EOL.WikiEOL.Wiki
← ← Back to all products

Dropwizard

Active
OtherLatest Version: 5.0.2Latest Release: May 31, 2026

Support summary

Dropwizard currently has supported cycles. Track the next EOL date and validate upgrades before your change window.

What do EOL and support statuses mean?

Next EOL

No announced EOL date is currently listed.

Supported cycles

1

0 lts

Versions

9

Latest Version

5.0.2

Active Support

1

EOL

8

Lifecycle Timeline

Today
5.0
5.0
4.0
4.0
3.0
3.0
2.1
2.1
2.0
2.0
1.3
1.3
1.2
1.2
1.1
1.1
1.0
1.0
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
5.0Sep 16, 2025YesNo5.0.2No
Active
4.0Mar 30, 2023NoJan 31, 20264.0.17No
EOL
3.0Mar 30, 2023NoJan 31, 20263.0.17No
EOL
2.1May 23, 2022NoJan 31, 20242.1.12No
EOL
2.0Dec 10, 2019NoJan 31, 20232.0.35No
EOL
1.3Mar 14, 2018NoDec 31, 20201.3.29No
EOL
1.2Oct 6, 2017NoYes1.2.9No
EOL
1.1Mar 22, 2017NoYes1.1.8No
EOL
1.0Jul 27, 2016NoYes1.0.9No
EOL

Data sources

Frequently Asked Questions

Which versions of Dropwizard have reached end of life?
The following Dropwizard versions have reached end of life and no longer receive security updates: 4.0, 3.0, 2.1, 2.0, 1.3, 1.2, 1.1, 1.0. It is recommended to upgrade to a supported version.
Is it safe to continue using Dropwizard 4.0?
Dropwizard 4.0 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 Dropwizard?
The latest version of Dropwizard is 5.0.2, released in the 5.0 release cycle.
How many versions of Dropwizard are currently supported?
Dropwizard currently has 1 actively supported version(s): 5.0.
When does Dropwizard 5.0 reach end of life?
Dropwizard 5.0 does not have a specific end-of-life date announced yet.
What should I do when Dropwizard reaches end of life?
When a Dropwizard 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.