update copy for LTS support as of 2026 (#2699)

Author: thisisjofrank

README.md

@@ -174,10 +174,10 @@ number of versions they need to think about), improve search indexing, and help
 us maintain the docs by keeping our build times faster.
 
 In general, we should only version the documentation **when we want to
-concurrently maintain several versions of the docs**, like for major/LTS
-versions. For example - the [Node.js docs](https://nodejs.org/en/docs) are only
-versioned for major releases, like `20.x` and `19.x`. We will adopt this pattern
-as well, and won't have versioned docs for patch or feature releases.
+concurrently maintain several versions of the docs**, like for major versions.
+For example - the [Node.js docs](https://nodejs.org/en/docs) are only versioned
+for major releases, like `20.x` and `19.x`. We will adopt this pattern as well,
+and won't have versioned docs for patch or feature releases.
 
 For additive changes, it should usually be sufficient to indicate which version
 a feature or API was released in. For example - in the Node 20 docs, the

runtime/fundamentals/stability_and_releases.md

@@ -33,22 +33,22 @@ Deno offers 4 release channels
 
 ### Long Term Support (LTS)
 
-Starting with Deno v2.1.0 (released in November 2024), Deno offers an LTS
-(long-term support) channel.
+:::warning
 
-An LTS channel is a minor semver version that we maintain with only
-backwards-compatible bug fixes.
+LTS support will be discontinued after April 30, 2026; there will be no LTS
+releases or maintenance beyond that date.
+
+:::
+
+Deno offers an LTS (long-term support) channel. This is a minor semver version
+that we maintain with only backwards-compatible bug fixes.
 
 | LTS release version | LTS maintenance start | LTS maintenance end |
 | ------------------- | --------------------- | ------------------- |
 | v2.1                | Feb 1st, 2025         | Apr 30th, 2025      |
 | v2.2                | May 1st, 2025         | Oct 31st, 2025      |
 | v2.4                | Nov 1st, 2025         | Apr 30th, 2026      |
 
-We are initially keeping the LTS support window short while we refine the
-process. **LTS releases occur every six months**, with patch releases as needed
-for bug fixes. We plan to extend this support window to one year in the future.
-
 LTS backports include:
 
 - Security patches
@@ -71,9 +71,10 @@ specifying file extensions.
 
 ## Standard library
 
-The Deno Standard Library (https://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.
+The Deno Standard Library ([jsr.io/@std](https://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

runtime/reference/migration_guide.md

@@ -37,17 +37,7 @@ deno.json:
 }
 ```
 
-[Read more on `Node.js support` page](/runtime/fundamentals/node/)
-
-### Long Term Support releases
-
-Starting with Deno v2.1.0 (to be released in November 2024) Deno will offer a
-LTS (long-term support) channel.
-
-An LTS version is supported for 6 months, receiving bug fixes and critical
-performance fixes before a new version is promoted to LTS.
-
-[Read more on `Stability and releases` page](/runtime/fundamentals/stability_and_releases/#long-term-support-(lts))
+[Read more on `Node.js support` page](/runtime/fundamentals/node/).
 
 ## Managing dependencies