mirror of https://github.com/nodejs/node.git synced 2024-11-24 20:29:23 +01:00

marsonya 0486cb86cd doc: apply sentence case to headers in doc/guides

PR-URL: https://github.com/nodejs/node/pull/37506
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Pooja D P <Pooja.D.P@ibm.com>
Reviewed-By: Harshitha K P <harshitha014@gmail.com>
Reviewed-By: Darshan Sen <raisinten@gmail.com>

2021-02-27 12:00:15 -08:00

1.2 KiB

Raw Blame History

Maintaining npm in Node.js

New pull requests should be opened when a "next" version of npm has been released. Once the "next" version has been promoted to "latest" the PR should be updated as necessary.

The specific Node.js release streams the new version will be able to land into are at the discretion of the release and LTS teams.

This process only covers full updates to new versions of npm. Cherry-picked changes can be reviewed and landed via the normal consensus seeking process.

Step 1: Run the update script

In the following examples, x.y.z should match the npm version to update to.

$ ./tools/update-npm.sh x.y.z

Step 2: Commit new npm

$ git add -A deps/npm
$ git commit -m "deps: upgrade npm to x.y.z"

Step 3: Update licenses

$ ./configure
$ make -j4
$ ./tools/license-builder.sh
# The following commands are only necessary if there are changes
$ git add .
$ git commit -m "doc: update npm LICENSE using license-builder.sh"

Note: please ensure you are only making the updates that are changed by npm.

Step 4: Apply whitespace fix

$ git rebase --whitespace=fix master

Step 5: Test the build

$ make test-npm

1.2 KiB Raw Blame History