You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/support/node-version.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Node version requirement
2
2
3
-
**semantic-release** is written using the latest [ECMAScript 2017](https://www.ecma-international.org/publications/standards/Ecma-262.htm) features, without transpilation which **requires Node version 20.8.1 or higher**.
3
+
**semantic-release** is written using the latest [ECMAScript 2017](https://www.ecma-international.org/publications/standards/Ecma-262.htm) features, without transpilation which **requires Node version 22.14.0 or higher**.
4
4
5
5
**semantic-release** is meant to be used in a CI environment as a development support tool, not as a production dependency.
6
6
Therefore, the only constraint is to run the `semantic-release` in a CI environment providing version of Node that meets our version requirement.
@@ -24,7 +24,7 @@ See [CI configuration](../usage/ci-configuration.md) and [CI configuration recip
24
24
Use it to execute the `semantic-release` command.
25
25
26
26
```bash
27
-
$ npx -p node@v18-lts -c "npx semantic-release"
27
+
$ npx -p node@v24 -c "npx semantic-release"
28
28
```
29
29
30
30
**Note**: See [What is npx](./FAQ.md#what-is-npx) for more details.
0 commit comments