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

Deno

Active
Runtimes & JDKs Latest Version: 2.8.2 Latest Release: Jun 3, 2026

Deno is a secure JavaScript and TypeScript runtime built on V8, designed as a modern alternative to Node.js.

Versions

10

Latest Version

2.8.2

Active Support

1

EOL

9

Lifecycle Timeline

Today
2.8
2.8
2.7
2.7
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

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
2.8May 22, 2026YesNo2.8.2No
Active
2.7Feb 25, 2026NoMay 22, 20262.7.14No
EOL
2.6Dec 10, 2025NoFeb 25, 20262.6.10No
EOL
2.5Sep 10, 2025NoApr 30, 20262.5.7
2025-11-01
EOL
2.4Jul 1, 2025NoSep 10, 20252.4.5No
EOL
2.3Apr 30, 2025NoJul 1, 20252.3.7No
EOL
2.2Feb 18, 2025NoOct 31, 20252.2.15
2025-05-01
EOL
2.1Nov 21, 2024NoApr 30, 20252.1.14
2025-02-01
EOL
2.0Oct 8, 2024NoNov 21, 20242.0.6No
EOL
1Apr 13, 2020NoOct 9, 20241.46.3No
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.7, 2.6, 2.5, 2.4, 2.3, 2.2, 2.1, 2.0 (and 1 more). It is recommended to upgrade to a supported version.
Is it safe to continue using Deno 2.7?
Deno 2.7 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.8.2, released in the 2.8 release cycle.
How many versions of Deno are currently supported?
Deno currently has 1 actively supported version(s): 2.8.
When does Deno 2.8 reach end of life?
Deno 2.8 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.