From 9a4e0bd9e658fc15d8ecef05200bf409a9f60469 Mon Sep 17 00:00:00 2001 From: Andre Wanlin Date: Thu, 31 Oct 2024 09:43:47 -0500 Subject: [PATCH 1/3] Updated Getting Started Node LTS Link Signed-off-by: Andre Wanlin --- docs/getting-started/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/getting-started/index.md b/docs/getting-started/index.md index 993cd7cbfd..926225724a 100644 --- a/docs/getting-started/index.md +++ b/docs/getting-started/index.md @@ -30,7 +30,7 @@ This guide assumes a basic understanding of working on a Linux based operating s On macOS, you will want to have run `xcode-select --install` to get the XCode command line build tooling in place. - An account with elevated rights to install the dependencies - `curl` or `wget` installed -- Node.js [Active LTS Release](https://nodejs.org/en/about/previous-releases) installed using one of these +- Node.js [Active LTS Release](../overview/versioning-policy.md#nodejs-releases) installed using one of these methods: - Using `nvm` (recommended) - [Installing nvm](https://github.com/nvm-sh/nvm#install--update-script) From a0db2f2fec28ad163e6fccd0d7a4b7d42aba8ee4 Mon Sep 17 00:00:00 2001 From: Andre Wanlin Date: Thu, 31 Oct 2024 09:46:50 -0500 Subject: [PATCH 2/3] Added sentence about release timing Signed-off-by: Andre Wanlin --- docs/overview/versioning-policy.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/docs/overview/versioning-policy.md b/docs/overview/versioning-policy.md index 2ae73e1383..52c6087674 100644 --- a/docs/overview/versioning-policy.md +++ b/docs/overview/versioning-policy.md @@ -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: From e1fa5ae9ed2878cb8b39848c50b5931d1ccb39fa Mon Sep 17 00:00:00 2001 From: Andre Wanlin Date: Mon, 18 Nov 2024 15:40:32 -0600 Subject: [PATCH 3/3] Refactor Signed-off-by: Andre Wanlin --- docs/overview/versioning-policy.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/overview/versioning-policy.md b/docs/overview/versioning-policy.md index 52c6087674..f5e2e222f8 100644 --- a/docs/overview/versioning-policy.md +++ b/docs/overview/versioning-policy.md @@ -166,7 +166,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. -- 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. +- 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: @@ -174,6 +177,8 @@ When we say _Supporting_ a Node.js release, that means the following: - New Backstage projects created with `@backstage/create-app` will have their `engines.node` version set accordingly. - Dropping compatibility with unsupported releases is not considered a breaking change. This includes using new syntax or APIs, as well as bumping dependencies that drop support for these versions. +Based on the above Backstage supports Node.js 20 and 22 as of the `1.33.0` release. + ## TypeScript Releases The Backstage project uses [TypeScript](https://www.typescriptlang.org/) for type checking within the project, as well as external APIs and documentation. It is important to have a clear policy for which TypeScript versions we support, since we want to be able to adopt new TypeScript features, but at the same time not break existing projects that are using older versions.