← ← Back to all products
Deno
Active
Runtimes & JDKs Latest Version: 2.6.9 Latest Release: Feb 10, 2026
Deno is a secure JavaScript and TypeScript runtime built on V8, designed as a modern alternative to Node.js.
Versions
8
Latest Version
2.6.9
Active Support
2
EOL
6
Lifecycle Timeline
Today ↓
2.6
2.6
2.5
2.5
2.4
2.4
2.3
2.3
2.2
2.2
2.1
2.1
2.0
2.0
1
1
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 2.6 | Dec 10, 2025 | - | No | 2.6.9 | No | Active |
| 2.5 | Sep 10, 2025 | - | Apr 30, 2026 | 2.5.7 | 2025-11-01 | Active |
| 2.4 | Jul 1, 2025 | - | Sep 10, 2025 | 2.4.5 | No | EOL |
| 2.3 | Apr 30, 2025 | - | Jul 1, 2025 | 2.3.7 | No | EOL |
| 2.2 | Feb 18, 2025 | - | Oct 31, 2025 | 2.2.15 | 2025-05-01 | EOL |
| 2.1 | Nov 21, 2024 | - | Apr 30, 2025 | 2.1.14 | 2025-02-01 | EOL |
| 2.0 | Oct 8, 2024 | - | Nov 21, 2024 | 2.0.6 | No | EOL |
| 1 | Apr 13, 2020 | - | Oct 9, 2024 | 1.46.3 | No | EOL |
Frequently Asked Questions
Which versions of Deno have reached end of life?
The following Deno versions have reached end of life and no longer receive security updates: 2.4, 2.3, 2.2, 2.1, 2.0, 1. It is recommended to upgrade to a supported version.
Is it safe to continue using Deno 2.4?
Deno 2.4 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 Deno?
The latest version of Deno is 2.6.9, released in the 2.6 release cycle.
How many versions of Deno are currently supported?
Deno currently has 2 actively supported version(s): 2.6, 2.5.
When does Deno 2.6 reach end of life?
Deno 2.6 does not have a specific end-of-life date announced yet.
What should I do when Deno reaches end of life?
When a Deno 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.