Skip to content

Commit af600f9

Browse files
committed
doc: use NODE_API_SUPPORTED_VERSION_MAX in release doc
The code was changed in nodejs#48501 but the doc was missed.
1 parent de4553f commit af600f9

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

doc/contributing/releases-node-api.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ release process.
99
* [0. Pre-release steps](#0-pre-release-steps)
1010
* [1. Update the main branch](#1-update-the-main-branch)
1111
* [2. Create a new branch for the release](#2-create-a-new-branch-for-the-release)
12-
* [3. Update `NAPI_VERSION`](#3-update-napi_version)
12+
* [3. Update `NODE_API_SUPPORTED_VERSION_MAX`](#3-update-node_api_supported_version_max)
1313
* [4. Define `addon_context_register_func`](#4-define-addon_context_register_func)
1414
* [5. Update version guards](#5-update-version-guards)
1515
* [6. Create release commit](#6-create-release-commit)
@@ -55,13 +55,13 @@ Create a new branch named `node-api-x-proposal`, off the main branch.
5555
git checkout -b node-api-10-proposal upstream/main
5656
```
5757

58-
### 3. Update `NAPI_VERSION`
58+
### 3. Update `NODE_API_SUPPORTED_VERSION_MAX`
5959

6060
Set the version for the proposed release using the following macros, which are
6161
already defined in `src/node_version.h`:
6262

6363
```c
64-
#define NAPI_VERSION x
64+
#define NODE_API_SUPPORTED_VERSION_MAX x
6565
```
6666
6767
> Note: Do not update the `NAPI_VERSION` defined in `src/js_native_api.h`. It

0 commit comments

Comments
 (0)