Skip to content

Commit 295317e

Browse files
committed
docs: clarify Alpha channel vs nightly builds in release schedule post
1 parent 3c1aa4e commit 295317e

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

apps/site/pages/en/blog/announcements/evolving-the-nodejs-release-schedule.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -48,17 +48,16 @@ This model follows a pattern similar to Ubuntu's release cycle: predictable Apri
4848

4949
### About the Alpha Channel
5050

51-
The Alpha channel replaces odd-numbered releases. During this period, only [nightly builds](https://nodejs.org/download/nightly/) are available for early testing.
51+
The Alpha channel replaces odd-numbered releases. Alpha releases are signed, tagged, and tested through CITGM. This is different from [nightly builds](https://nodejs.org/download/nightly/), which remain available as automated untested builds from main.
5252

5353
**Who it's for:** Library authors and CI pipelines testing compatibility with upcoming breaking changes. Not intended for production use.
5454

5555
**What to expect:**
56-
5756
- Semver-major changes land during this phase
58-
- No security patches (only stable releases receive security fixes)
59-
- API may change between builds
57+
- Releases are signed and tagged (unlike nightly)
58+
- API may change between releases
6059

61-
**Why:** Provides early feedback on breaking changes without maintaining another full release line. Also allows landing V8 updates earlier in the cycle, so we don't ship a single V8 version per year.
60+
**Why:** Provides early feedback on breaking changes with quality gates that nightly builds lack. Also allows landing V8 updates earlier in the cycle.
6261

6362
## What's NOT Changing
6463

0 commit comments

Comments
 (0)