GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — doc: clarify release process for new releasers · nodejs/node@2815bd3

File tree

Expand file treeCollapse file tree
Open diff view settings
Filter options
  • doc/contributing
    • releases.md
Expand file treeCollapse file tree
Open diff view settings
Collapse file

‎doc/contributing/releases.md‎

Copy file name to clipboardExpand all lines: doc/contributing/releases.md
+16-1Lines changed: 16 additions & 1 deletion
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -468,7 +468,20 @@ failed build if you start again!
468468
Jenkins collects the artifacts from the builds, allowing you to download and
469469
install the new build. Make sure that the build appears correct. Check the
470470
version numbers, and perform some basic checks to confirm that all is well with
471-
the build before moving forward.
471+
the build before moving forward. Use the following list as a baseline:
472+
473+
* `process.version` is as expected
474+
* `process.release` is as expected
475+
* `process.versions` is as expected (for example, `openssl` or `llhttp` version
476+
must be in the expected updated version)
477+
* npm version (check it matches what we expect)
478+
* Run the test suite against the built binaries (optional)
479+
480+
```console
481+
./tools/test.py --shell ~/Downloads/node-v18.5.0-linux-x64/bin/node
482+
```
483+
484+
<sup>There may be test issues if the branch used to test does not match the Node.js binary.</sup>
472485

473486
### 11. Tag and sign the release commit
474487

@@ -510,6 +523,8 @@ include the release code name.
510523
The tag **must** be signed using the GPG key that's listed for you on the
511524
project README.
512525

526+
**Note**: Don't push the tag to remote at this point.
527+
513528
### 12. Set up for the next release
514529

515530
On release proposal branch, edit `src/node_version.h` again and:

0 commit comments

Comments
0 (0)
You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.