Skip to content

Commit d37fe88

Browse files
avivkellerMattIPv4
andauthored
Apply suggestions from code review
Co-authored-by: Matt Cowley <me@mattcowley.co.uk>
1 parent 0743036 commit d37fe88

1 file changed

Lines changed: 7 additions & 5 deletions

File tree

incidents/2026-04-01.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,11 +3,11 @@
33
- Incident Commander: @MattIPv4
44
- Severity Level: P2
55

6-
For a brief period of time, the downloads page was blank due to a false assumption on there always being a Current version of Node.
6+
For a brief period of time, the `/downloads/current` page was blank due to a logic bug in determining the Current version of Node.js. The main `/downloads` page was unaffected and could be accessed throughout.
77

88
## Timeline
99

10-
- **2025-04-01 12:00 AM UTC**: Start of impact. Node.js v25.x expected to move from Current to Active LTS.
10+
- **2025-04-01 12:00 AM UTC**: Start of impact. Release schedule indicates that Node.js 25.x has moved from Current to Active LTS.
1111

1212
- **2025-04-01 00:14 AM UTC**: Impact identified by [@MattIPv4's monitoring action](https://github.com/MattIPv4/monitors/actions/runs/23825485542).
1313

@@ -23,13 +23,15 @@ For a brief period of time, the downloads page was blank due to a false assumpti
2323

2424
Users navigating to `https://nodejs.org/en/download/current` would see a blank page instead of the proper download instructions.
2525

26+
Users accessing any page on the website would see only the 24.x LTS release in the footer, no Current release.
27+
2628
`https://nodejs.org/en/download` was unaffected by this issue.
2729

2830
## Root Cause
2931

30-
According to a static schedule, on April 1st, 2026, Node.js 25.x was expected to move from Current to Active LTS, however, with v26.x
31-
[still unreleased](https://github.com/nodejs/node/pull/62526), this left no Current release left, causing the website to not properly
32-
render components relying on the Current release of Node.js.
32+
According to the static release schedule, on April 1st, 2026, Node.js 25.x was expected to move from Current to Active LTS. Due to this, the website logic automatically started treating 25.x as an Active LTS major.
33+
34+
However, no new release of 25.x has yet been made to be marked as LTS, nor has the first release of 26.x been made to become the new Current major. This left the website with no Current release per its logic.
3335

3436
## Fix
3537

0 commit comments

Comments
 (0)