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

Added sentence about release timing

Browse Source 
Signed-off-by: Andre Wanlin <awanlin@spotify.com>
This commit is contained in:
Andre Wanlin
2024-10-31 09:46:50 -05:00
parent 9a4e0bd9e6
commit a0db2f2fec
1 changed files with 1 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/overview/versioning-policy.md
+1 -4
View File
@@ -166,10 +166,7 @@ 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.
- 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.
- 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. This support will come in the first Backstage main release line release after a Node.js release becomes _Active LTS_. 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: