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.

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

deps: upgrade npm to 5.0.0 #13276

Closed
wants to merge 1 commit into from
Closed

deps: upgrade npm to 5.0.0 #13276

wants to merge 1 commit into from

Conversation

zkat
Copy link
Contributor

@zkat zkat commented May 29, 2017

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines
Affected core subsystem(s)
  • deps
Description of Changes

This is the final version of npm@5.0.0! It's pretty much the same as the beta.56 release that was submitted before, but has some bugfixes from the rest of the beta. We went kinda fast so I don't have a concrete list of changes since then, but you can check the new changelog for overall details.

Please note that npm5 is a major update to npm, and is still fairly young. I fully expect users to find all sorts of doozies, even after a month of beta, and even longer of internal testing. We'll be doing tighter release cycles while npm5 stabilizes, though, and update-notifier should help users keep up to date even if new versions take a few more days to land in node@8. This is mostly a general comment about Super Fresh™ software.

I want to thank y'all on the node team for keeping this window open and being communicative with the npm team about your needs/expectations. I feel pretty good about this release even with the deadline having been so tight. 🎉

Note: tomorrow is a company holiday, but I've shifted my day off to Friday so I can be available to help get this release out the door. Please do let me know if you ned anything.

Changelog

@nodejs-github-bot nodejs-github-bot added the npm Issues and PRs related to the npm client dependency or the npm registry. label May 29, 2017
@bricss bricss mentioned this pull request May 29, 2017
@jasnell jasnell added this to the 8.0.0 milestone May 29, 2017
@jasnell
Copy link
Member

jasnell commented May 29, 2017

@nodejs/ctc @nodejs/collaborators @nodejs/npm ... we'll need to fast track this to land today in order to make it in to the 8.0.0 release.

Copy link
Member

@jasnell jasnell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rubber stamp LGTM

Copy link
Contributor

@cjihrig cjihrig left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also rubber stamp LGTM

@Fishrock123
Copy link
Contributor

Taking a look now.

@Fishrock123
Copy link
Contributor

Seems good. As a note, more tests are now skipped on my machine:

total ........................................... 4417/4428

  4417 passing (9m)
  11 pending

Previously, only one was. (The couchdb one(s) I think.)

@Fishrock123 Fishrock123 reopened this May 29, 2017
Copy link
Contributor

@Fishrock123 Fishrock123 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(That was not the button I was looking for.)

@addaleax
Copy link
Member

Landed in c58cea5

@addaleax addaleax closed this May 29, 2017
jasnell pushed a commit that referenced this pull request May 29, 2017
PR-URL: #13276
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
@zkat
Copy link
Contributor Author

zkat commented May 29, 2017

The skipped tests are pretty safe. They're just placeholders in @iarna's file specifier tests that haven't been filled in yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
npm Issues and PRs related to the npm client dependency or the npm registry.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants