As of Deno 1.0.0, the Deno namespace APIs are stable. That means we will strive to make code working under 1.0.0 continue to work in future versions.

Release schedule, channels, and long term support Jump to heading#

Deno releases a new stable, minor version (eg. v2.1.0, v2.0.0) on a 12 week schedule.

Patch releases including bug fixes for the latest minor version are released as needed - you can expect several patch releases before a new minor version is released.

Release channels Jump to heading#

Deno offers 3 release channels

• stable - a semver minor/patch release, as described above. This is the default distribution channel that is recommended for most users.
• rc - a release candidate for the upcoming semver minor release.
• canary - an unstable release that changes multiple times per day, allows to try out latest bug fixes and new features that might end up in the stable channel.

An lts (long term support) channel was previously offered, but it has been discontinued. See below for details.

Long Term Support (LTS) - discontinued Jump to heading#

From February 2025 to April 2026, Deno offered an LTS (long-term support) channel: a minor semver version maintained with only backwards-compatible bug fixes. The final LTS release was v2.5, which reached end of life on April 30, 2026.

LTS backports included:

• Security patches
• Critical bug fixes (e.g., crashes, incorrect computations)
• Critical performance improvements, backported based on severity

API changes and major new features were not backported.

Unstable APIs Jump to heading#

When introducing new APIs, these are first marked as unstable. This means that the API may change in the future. These APIs are not available to use unless you explicitly pass an unstable flag, like --unstable-kv. Learn more about --unstable-* flags.

There are also some non-runtime features of Deno that are considered unstable, and are locked behind unstable flags. For example, the --unstable-sloppy-imports flag is used to enable importing code without specifying file extensions.

Standard library Jump to heading#

The Deno Standard Library (jsr.io/@std) is mostly stable. All standard library modules that are version 1.0.0 or higher are considered stable. All other modules (0.x) are considered unstable, and may change in the future.

Using unstable standard library modules is not recommended for production code, but it is a great way to experiment with new features and provide feedback to the Deno team. It is not necessary to use any unstable flags to use unstable standard library modules.