Deno Gets 12 Months of Releases and Deploy Gets Six After Cloudflare Deal, and Two Forks Appear
Software / analysis
Deno Gets 12 Months of Releases and Deploy Gets Six After Cloudflare Deal, and Two Forks Appear
Feature pull requests are being closed unmerged, and the community fork called Ende wants to drop the Node compatibility that Ryan Dahl now calls a constraint.

Cloudflare hired the whole Deno team on Oct. 9, and the runtime that Ryan Dahl built as a cleaner Node.js now has an announced end date: monthly bug-fix and security releases for one year, then nothing from its original maintainers. Deno Deploy, the hosting service, shuts down in six months.
Two community forks, Ende and Dodo, appeared within ten days. Neither has shipped a release.
What Dahl's post commits to, and what it leaves out
Dahl, who created both Node.js and Deno, wrote on the Deno blog that "the entire Deno team is joining Cloudflare." The runtime stays open source and will be supported for one more year. Deploy runs for six months, and paying customers get migration help to Cloudflare Workers.
JSR, the package registry, keeps running with its infrastructure moving to Cloudflare, and the team will keep supporting rusty_v8 while working to integrate it into workerd, Cloudflare's open-source Workers runtime. The post gives no date for either. It also gives no customer count and says nothing about Fresh, the web framework, or Deno Sandbox.

The post names no Deploy shutdown date. Six months from Oct. 9 is early April 2027, but the post does not say so.
- Deno Deploy runs6 months
- Deno runtime bug-fix and security releases12 months
Source: Deno blog post by Ryan Dahl, accessed 2026-10-19
What the maintainers' own plan stops
A pinned GitHub issue, #37030, opened Oct. 15 by the contributor @bartlomieju, spells out the year. The Deno Company, now part of Cloudflare, will maintain Deno "until October 2027" through monthly 2.9.x LTS releases, with canary builds still published automatically from main.
Feature development stops. Feature pull requests will be closed without merging, while well-written bug-fix pull requests will still be reviewed. Canary-only features added after the 2.9 branch was cut will be reverted so that main matches 2.9. The issue names deno sync-types and the removal of Deno's internal TypeScript fork as examples, and promises a full list later.
What happens after October 2027 is, in the issue's words, still under consideration. Commenters have proposed a new foundation or a home at the OpenJS Foundation. No decision is recorded.
| Item | Fate | Date or window |
|---|---|---|
| Deno Deploy | Shuts down | Six months from Oct. 9, 2026 |
| Deno runtime | Monthly 2.9.x LTS fixes only | Until October 2027 |
| Feature pull requests | Closed unmerged | From Oct. 15, 2026 |
| JSR | Keeps running on Cloudflare | No date given |
Why Dahl says Node compatibility was the problem
Socket, the security company, reported on Oct. 16 that Dahl called the decision joint and said he no longer thinks Deno is where he can do his most important work. Socket quotes him: "We'll ship monthly releases for a year, and Deno stays MIT-licensed. If people want to carry it forward, I'd like that."
The blog post by the Ende fork's author quotes Dahl on the product itself: "It has been sucked into the gravity well of node compatibility, which forces it to behave exactly as Node does." Compatibility drove adoption, and Socket reports that Dahl's 2025 post said adoption more than doubled after Deno 2. It is also the feature the main fork wants to remove.
Socket also reports that Kenton Varda of Cloudflare said releasing workerd and hoping the community would build around it was naive. Dahl and Bert Belder will lead an effort to merge celld, a self-hosting implementation of the Workers and Durable Objects model that Deno released in August, into workerd.
Ende and Dodo: what each fork says it will do
Ende is proposed by Paul Webb, who writes the webb blog. It would drop Node compatibility and the Deploy, KV and Jupyter features. Its roadmap lists per-module permissions, sandboxes for untrusted code, post-quantum cryptography in Web Crypto and better binary output, and it replaces semantic versioning with ChronVer.
The post names no licence for Ende. It says ende.sh is a placeholder site with a mailing list, with a soft launch targeted for December and development on a host called EOL. Socket reports that a community server for the fork drew more than 100 active members in 48 hours.
Dodo, per Socket, is an earlier-stage effort to consolidate components spread across repositories. It has no releases and must be built from source.
The stakes are not only Deno's. Socket notes that Netlify and Supabase build their edge functions on Deno, and that Anthropic bought the Bun runtime in December 2025, when Bun's creator Jarred Sumner said it had no revenue. Deno raised $4.9 million in seed funding in 2021 and a $21 million Series A in 2022, per Socket.
Small open-source toolchains face the same question of who merges after the sponsor leaves. Lean 4.35 and the Free Pascal dynamic-packages fork are two this site has covered.
The next fixed date is the first monthly 2.9.x LTS release after Oct. 15, and the next unknown is Ende's December soft launch, which has no repository to check yet.
Sources
More in Software
- 01Rust's Two Biggest Compiler Projects Carry No Dates; the Measured Speed-Up Came From LLVM 23A compiler contributor's October 19 roundup and the Rust project's own goal pages agree on the list. They disagree on how much of it is measured.
- 02Mastodon 5.0 Moves the Composer to Bottom-Centre and Puts Stable Release 'a Few Weeks' OutThe project's October 19 design post lists what changed since the August preview and what was cut. Search, Settings, Messages and Notifications are still on the old interface.
- 03iPadOS 27 Gives the AirPlay Screen to Whichever App You Tapped Last, and Keynote Quits the ShowAn educator's Feedback report, FB23615646, describes presenter notes and unrevealed poll results appearing on a classroom screen. Apple's Keynote guide documents a presenter display for notes, a timer and a next-slide preview.
- 04Google Cloud's London Zone Went Down at 06:08 UTC. Its Status Page Waited 2 Hours 27 MinutesGoogle's incident log for europe-west2-b names a power event as the cause only at 11:12 UTC, five hours into an outage that ended at 14:00 UTC and reached Revolut, Lloyds and Royal Mail.