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

Refactor

Browse Source 
Signed-off-by: Andre Wanlin <awanlin@spotify.com>
This commit is contained in:
Andre Wanlin
2024-11-18 15:40:32 -06:00
parent a0db2f2fec
commit e1fa5ae9ed
1 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/overview/versioning-policy.md
+6 -1
View File
@@ -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.