new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Deno · Fundamentals · all subjects

stability

12 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Deno namespace APIs stable since 1.0.0

As of Deno 1.0.0, the Deno namespace APIs are stable. Code written for 1.0.0 is guaranteed to continue working in future versions.

Deno release schedule

Deno releases a new stable minor version (e.g., v2.1.0, v2.0.0) on a 12-week schedule. Patch releases with bug fixes for the latest minor version are released as needed, with several patch releases typically occurring before a new minor version is released.

Deno release channels

Deno is distributed on four release channels, each with its own latest version and download location. The stable channel provides semver minor and patch releases and is the default recommended for most users. The lts channel provides long-term support with only backwards-compatible bug fixes. The rc channel is a release candidate for the upcoming minor release. The canary channel is an unstable build that changes multiple times per day. During major-version prerelease cycles, Deno also publishes alpha and beta channels.

Stable, rc, and canary channel downloads

Stable builds are downloaded from GitHub releases. The rc, canary, alpha, and beta channels are served from Deno's download server at dl.deno.land.

Channel is baked into Deno binary

An installed Deno binary belongs to exactly one channel, which is baked into the binary when it is built. The deno upgrade command reads the current binary's channel to determine what latest means.

Version number does not identify channel

The same version number can exist as two different byte-different builds on different channels. For example, version 2.9.3 exists as both a stable release and an LTS release, built from the same source and carrying the same version string, differing only in an embedded channel marker and download location. A bare version number always resolves to the stable build.

deno upgrade command channel resolution table

deno upgrade resolves to latest stable release and installs a stable build. deno upgrade 2.9.3 resolves to version 2.9.3 on the stable channel and installs a stable build. deno upgrade lts resolves to latest lts release and installs an lts build. deno upgrade rc resolves to latest rc release and installs an rc build. deno upgrade canary resolves to latest canary build and installs a canary build. deno upgrade <git-hash> resolves to that specific canary build and installs a canary build.

Switching Deno channels with deno upgrade

To switch channels intentionally, pass the channel name to deno upgrade, for example deno upgrade lts or deno upgrade stable. A plain version number always selects the stable build, so a user on LTS running deno upgrade 2.9.3 will download the stable build and move off the lts channel onto stable. To stay on LTS, upgrade with deno upgrade lts. A channel name always resolves to that channel's newest build, so there is no way to pin an older LTS patch version.

Deno LTS channel active version and support timeline

The LTS channel is active on the Deno 2.9 line starting with v2.9.3 and is maintained until January 31st, 2027. Previous LTS releases: v2.1 maintained from Feb 1st, 2025 to Apr 30th, 2025; v2.2 from May 1st, 2025 to Oct 31st, 2025; v2.5 from Nov 1st, 2025 to Apr 30th, 2026; v2.9 from Jul 1st, 2026 to Jan 31st, 2027.

LTS backport policy

LTS backports include security patches, critical bug fixes such as crashes or incorrect computations, and critical performance improvements may be backported based on severity. API changes and major new features will not be backported.

Unstable APIs require explicit flags

When introducing new APIs, these are first marked as unstable and may change in the future. Unstable APIs are not available unless explicitly enabled by passing an unstable flag like --unstable-kv. Some non-runtime Deno features are also unstable and locked behind unstable flags, such as --unstable-sloppy-imports which enables importing code without specifying file extensions.

Deno Standard Library stability

The Deno Standard Library at jsr.io/@std is mostly stable. Standard library modules at version 1.0.0 or higher are considered stable. All other modules at version 0.x are considered unstable and may change in the future. Using unstable standard library modules is not recommended for production code but is a good way to experiment and provide feedback. No unstable flags are required to use unstable standard library modules.

Give your agent this brain