paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 32 Packages Projects Releases Wiki Activity

docs: update node versioning policy to be less optimistic

Browse Source 
Signed-off-by: Patrik Oldsberg <poldsberg@gmail.com>
This commit is contained in:
Patrik Oldsberg
2022-11-03 11:07:58 +01:00
parent 27d51f80d8
commit 4befb8d638
1 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/overview/versioning-policy.md
+4 -3
View File
@@ -144,9 +144,10 @@ following schedule for determining the [Node.js releases](https://nodejs.org/en/
- At any given point in time we support exactly two adjacent even-numbered
releases of Node.js, for example v12 and v14.
- Three months before a Node.js release becomes _Active LTS_ we switch support
to that release and the previous one. This is halfway through the _Current LTS_
cycle for that release and occurs at the end of July every year.
- Once a new Node.js release becomes _Active LTS_ we switch to support that
release and the previous one. The switch is not immediate but done as soon
as possible. You can find the Node.js version supported by each release
in the `engines` field in the root `package.json` of a new app.
When we say _Supporting_ a Node.js release, that means the following: