Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

doc: add policy for landing new npm releases #21594

Closed
wants to merge 2 commits into from
Closed

doc: add policy for landing new npm releases #21594

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b1a3931
doc: add policy for landing new npm releases
MylesBorins Jun 29, 2018
6db6b53
fixup: minor grammar nits
MylesBorins Jul 11, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions doc/guides/maintaining-npm.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,19 @@
# 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.

Two weeks after the "latest" release has been promoted it can land on master
assuming no major regressions are found. There is no additional constraints
for Semver-Major releases.

The Node.js release streams the new version will 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: Clone npm

```console
Expand Down