The Internals of Deno
  • The Internals of Deno
  • Audience
  • Reviews
  • Translations
  • Formats
  • Contents
  • Chapter 1 - INTRODUCTION
    • 1.0 Cover page
    • 1.1 Introduction
    • 1.2 History of Deno
    • 1.3 About Deno
    • 1.4 Releases
    • 1.5 The Deno Company
    • 1.6 Deno's source
    • 1.7 What's next
  • Chapter 2 - ARCHITECTURE
    • 2.0 Cover page
    • 2.1 Architecture
    • 2.2 Overall architecture
    • 2.3 Programming Languages
    • 2.4 Deno components
    • 2.5 OPs
    • 2.6 TSC/SWC
    • 2.7 Rusty_v8
    • 2.8 Tokio
    • 2.9 V8
    • 2.10 What's next
  • CHAPTER 3 - THREADING MODEL
    • 3.0 Cover page
    • 3.1 Threading model
    • 3.2 Default threading model
    • 3.3 Asynchronous green threads
    • 3.4 What's next
  • CHAPTER 4 - BRIDGE
    • 4.0 Cover page
    • 4.1 The bridge
    • 4.2 Print
    • 4.3 Encode and decode
    • 4.4 What's next
  • CHAPTER 5 - FOUNDATIONS
    • 5.0 Cover page
    • 5.1 Hello world program
    • 5.2 Basic hello world
    • 5.3 Main program of Deno
    • 5.4 Module Specifier
    • 5.5 CLI Factory
    • 5.6 Permissions
    • 5.7 Main Worker
    • 5.8 JS Runtime
    • 5.9 Run main module
    • 5.10 Load module
    • 5.11 Recursive module loading
    • 5.12 Module graphs
    • 5.13 File fetching
    • 5.14 Transpile
    • 5.15 Register / compile module
    • 5.16 Instantiate module
    • 5.17 Evaluate module
    • 5.18 What's next
  • CHAPTER 6 - IMPORTS AND OPS
    • 6.0 Cover page
    • 6.1 Imports and ops
    • 6.2 Hello world program v2
    • 6.3 Module graph with imports
    • 6.4 Transpile
    • 6.5 Registration and instantiation
    • 6.6 Registration of ops
    • 6.7 Evaluate module
    • 6.8 Sync OPs
    • 6.9 Debug logs
    • 6.10 What's next
  • CHAPTER 7 - LOCAL AND SESSION STORAGE
    • 7.0 Cover page
    • 7.1 Introduction
    • 7.2 Local storage
    • 7.3 Session storage
    • 7.4 What's next
  • AFTERWORD
    • Afterword
Powered by GitBook
On this page
  • First release
  • Subsequent releases
  • Release schedule
  1. Chapter 1 - INTRODUCTION

1.4 Releases

Previous1.3 About DenoNext1.5 The Deno Company

Last updated 9 months ago

First release

The concept of Deno was first introduced in 2018, followed by an intensive development phase that lasted approximately two years. The first official release of Deno, version 1.0.0, occurred on May 13, 2020. Although this initial release contained many bugs, it demonstrated the effectiveness and functionality of the platform.

Following the successful launch, Deno adopted a regular release schedule, issuing both major and minor updates on a predetermined timetable. This iterative approach enabled Deno to evolve and improve over time, addressing issues and enhancing its capabilities with each successive release. This consistent development and release pattern have contributed to Deno's growth and maturation as a robust and reliable platform.

Subsequent releases

The development of Deno continues at a steady and deliberate pace, with a focus on sustainability and reliability. The Deno repository on GitHub remains highly active, with frequent updates and contributions from the development team on a nearly daily basis. This consistent activity demonstrates the team's dedication to the project's ongoing advancement. The development team is committed to a meticulous and thoughtful approach to enhancements and releases, ensuring a steady and incremental evolution of Deno's capabilities. This approach prioritizes stability and quality, reflecting the team's dedication to maintaining a high standard of excellence in the project's development.

Release schedule

Since its initial launch, Deno has undergone 45 significant updates, accompanied by numerous smaller revisions. Currently, Deno operates within the 1.x release framework. As of July 2024, discussions are underway regarding the upcoming release of Deno 2.0, expected later in the year.

As Deno continues to evolve, its development pace is now more rigorously managed. Each major and minor release integrates new features, solutions, and bug fixes, contributing to the platform's maturation. The scope of these updates is substantial, making it challenging to enumerate each individual change due to their abundance. The frequent releases demonstrate the dedication of the development team to maintaining a robust and reliable platform. The ongoing progress and development of Deno ensure its continued growth and improvement.

A comprehensive record of all releases can be found on the dedicated GitHub page: . These releases, denoted by version numbers such as 1.1.0, 1.2.0, 1.3.0, 1.36.0, and 1.45.0, are issued approximately monthly. Major releases are accompanied by official blog posts, accessible at , which detail advancements and changes. Minor releases, indicated by version numbers like 1.major.minor, occur every 2-8 days, typically following a weekly schedule unless urgent issues require a prompt response.

https://github.com/denoland/deno/releases/
https://deno.com/blog