← ← Back to all products
Docusaurus
Active
Tools & Monitoring Latest Version: 3.10.1 Latest Release: Apr 30, 2026
Docusaurus is a React-based static-site generator from Meta, optimized for building documentation websites. Active development and patches focus on the latest 3.x minor lines.
Versions
7
Latest Version
3.10.1
Active Support
2
EOL
5
Lifecycle Timeline
Today ↓
3.10
3.10
3.9
3.9
3.8
3.8
3.7
3.7
3.6
3.6
3.0
3.0
2.0
2.0
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 3.10 | Apr 7, 2026 | Yes | No | 3.10.1 | No | Active |
| 3.9 | Sep 25, 2025 | Yes | No | 3.9.2 | No | Active |
| 3.8 | May 27, 2025 | No | Yes | 3.8.1 | No | EOL |
| 3.7 | Jan 3, 2025 | No | Yes | 3.7.0 | No | EOL |
| 3.6 | Nov 4, 2024 | No | Yes | 3.6.3 | No | EOL |
| 3.0 | Oct 31, 2023 | No | Yes | 3.0.1 | No | EOL |
| 2.0 | Aug 1, 2022 | No | Yes | 2.4.3 | No | EOL |
Frequently Asked Questions
Which versions of Docusaurus have reached end of life?
The following Docusaurus versions have reached end of life and no longer receive security updates: 3.8, 3.7, 3.6, 3.0, 2.0. It is recommended to upgrade to a supported version.
Is it safe to continue using Docusaurus 3.8?
Docusaurus 3.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 Docusaurus?
The latest version of Docusaurus is 3.10.1, released in the 3.10 release cycle.
How many versions of Docusaurus are currently supported?
Docusaurus currently has 2 actively supported version(s): 3.10, 3.9.
When does Docusaurus 3.10 reach end of life?
Docusaurus 3.10 does not have a specific end-of-life date announced yet.
What should I do when Docusaurus reaches end of life?
When a Docusaurus 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.