doc: improve the workflow to test release binaries

PR-URL: #45004 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: James M Snell <[email protected]>
nodejs · Nov 10, 2022 · e6bbc50 · e6bbc50
1 parent 43677e5
commit e6bbc50
Showing 1 changed file with 3 additions and 2 deletions.
diff --git a/doc/contributing/releases.md b/doc/contributing/releases.md
@@ -603,13 +603,14 @@ the build before moving forward. Use the following list as a baseline:
   must be in the expected updated version)
 * npm version (check it matches what we expect)
 * Run the test suite against the built binaries (optional)
+  * Remember to use the proposal branch
+  * Run `make build-addons` before running the tests
+  * Remove `config.gypi` file
 
 ```console
 ./tools/test.py --shell ~/Downloads/node-v18.5.0-linux-x64/bin/node
 ```
 
-<sup>There may be test issues if the branch used to test does not match the Node.js binary.</sup>
-
 ### 11. Tag and sign the release commit
 
 Once you have produced builds that you're happy with, create a new tag. By