Skip to content

Commit 48023fc

Browse files
committed
Update release plan
1 parent 32b9566 commit 48023fc

File tree

3 files changed

+23
-27
lines changed

3 files changed

+23
-27
lines changed

about/releases/index.md

Lines changed: 14 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -4,27 +4,24 @@ title: Release Plan
44
slug: releases
55
---
66

7-
_Updated: 2022-08-04_
7+
_Updated: 2024-01-03_
88

99
This plan is a guide for how the project plans to schedule upcoming releases, taking
1010
into account the release schedule of the underlying Node.js runtime.
1111

1212
![](release-plan.png)
1313

14+
The project aims to make a new major release around April each year. This aligns
15+
with when versions of Node.js reach their end-of-life and enables us to drop support
16+
for them.
1417

15-
The active Node-RED stream (3.x) will get a new minor version release (for example, 3.1 -> 3.2)
16-
every three months. Maintenance releases (for example 3.1.0 -> 3.1.1) will continue
17-
to happen as and when they are needed.
18+
The active Node-RED stream will get regular minor releases (for example 4.0 -> 4.1)
19+
containing new features as well as maintenance releases (for example 4.0.1 -> 4.0.2)
20+
as and when they are needed.
1821

19-
At the end of April 2023, when Node 14.x reaches its end-of-life, we will publish
20-
Node-RED 4.x that will *drop* support for Node 14.
21-
22-
The 3.x stream will then enter maintenance mode. It will only receive bug fixes
23-
and security updates. New features could get back-ported from 4.x if there was
24-
a very good reason to do so as well as people available to do the work.
25-
26-
The 4.x stream will continue in active development with a minor release every
27-
three months or so for a year, when the next major release is made.
22+
When a new major version is released, the previous version enters maintenance mode
23+
for an extended period of time. During this time it will only receive bug fixes
24+
and security updates.
2825

2926
This proposal means:
3027

@@ -36,12 +33,12 @@ This proposal means:
3633

3734
Release | Initial | Maintenance Start | End-of-life
3835
--------|-----------------|----------------------|-----------------
39-
1.x | 2019-09-30 | 2021-04-30 | 2022-06-30
36+
4.x | *2024-04-30* * | *2025-04-30* * | 2026-06-30
37+
3.x | 2022-07-14 | *2024-04-30* * | 2025-06-30
4038
2.x | 2021-07-22 | 2022-07-14 | 2023-06-30
41-
3.x | 2022-07-14 | *2023-04-30* * | 2024-06-30
42-
4.x | *2023-04-30* * | *2024-04-30* * | 2025-06-30
39+
1.x | 2019-09-30 | 2021-04-30 | 2022-06-30
4340

44-
_* Dates are subject to change_
41+
_Dates are subject to change_
4542

4643
References:
4744
- [Blog post: Going beyond Node-RED 1.x](https://nodered.org/blog/2020/07/01/release-plans)

about/releases/release-plan.png

-6.05 KB
Loading

docs/faq/node-versions.md

Lines changed: 9 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -5,23 +5,22 @@ title: Supported Node versions
55
slug: node versions
66
---
77

8-
Node-RED currently recommends **Node 18.x or Node 20.x**.
8+
_Updated: 2024-01-03_
99

10-
Version | Support Level | Notes
11-
-----------|-----------------|------
12-
**20.x** | **Recommended** |
13-
**18.x** | **Recommended** |
14-
16.x | *Supported* |
15-
14.x | *Supported* | Node-RED 3.x or earlier only
16-
12.x | *Supported* | Node-RED 2.x or earlier only
17-
< 10.x | *Unsupported* | Node-RED 1.x or earlier only
10+
Node-RED currently recommends **Node 20.x**.
1811

1912
We try to stay up to date with Node.js releases. Our goal is to support
2013
the [Maintenance and Active LTS releases](https://nodejs.org/en/about/releases/).
2114

22-
We do not generally recommend using the odd numbered Node.js versions - we do not
15+
We do not recommend using the odd numbered Node.js versions - we do not
2316
routinely test against them.
2417

18+
Node-RED Version | Minimum Node.js Version
19+
---|---
20+
4.x | 18
21+
3.x | 14
22+
2.x | 12
23+
2524
With such a large community of 3rd party nodes available to install, we cannot
2625
provide any guarantees on what they support. We rely on the community to keep
2726
up to date.

0 commit comments

Comments
 (0)