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 2.14.9 (for v4.x-staging) #3686

Closed
wants to merge 1 commit into from

Conversation

othiym23
Copy link
Contributor

@othiym23 othiym23 commented Nov 6, 2015

(Second verse, same as the first.)

Mostly just dependency upgrades and some small typo fixes. make test-npm passed, but again I'd like independent confirmation before merging.

r: @Fishrock123

@othiym23 othiym23 added npm Issues and PRs related to the npm client dependency or the npm registry. land-on-v4.x labels Nov 6, 2015
@othiym23
Copy link
Contributor Author

othiym23 commented Nov 6, 2015

I see the whitespace issues, and will rebase / apply the whitespace fix and push again.

Dependency upgrades.
@othiym23
Copy link
Contributor Author

othiym23 commented Nov 6, 2015

Whitespace fix applied, and force-pushed. Also, reminded myself to read the release process docs more carefully in the future. ;)

@MylesBorins
Copy link
Contributor

All tests passing on my local machine 10.10.5 (make && make test-npm)

@Fishrock123
Copy link
Contributor

@thealphanerd That's not necessarily accurate. Pre npm 3 (i.e. pre-v5.x) you need to also do (sudo) make install, as sometimes npm will be using the global node (and possibly itself).

@Fishrock123
Copy link
Contributor

LGTM

@MylesBorins
Copy link
Contributor

thanks for the heads up @Fishrock123

@jasnell
Copy link
Member

jasnell commented Nov 9, 2015

LGTM

@jasnell
Copy link
Member

jasnell commented Nov 9, 2015

Will get this landed in v4.x-staging a bit later this week.

othiym23 added a commit that referenced this pull request Nov 15, 2015
Dependency upgrades.

PR-URL: #3686
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
@jasnell
Copy link
Member

jasnell commented Nov 15, 2015

Landed in v4.x-staging in 44d4a02

@jasnell jasnell closed this Nov 15, 2015
othiym23 added a commit that referenced this pull request Dec 4, 2015
Dependency upgrades.

PR-URL: #3686
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
@jasnell jasnell mentioned this pull request Dec 17, 2015
othiym23 added a commit that referenced this pull request Dec 17, 2015
Dependency upgrades.

PR-URL: #3686
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
@ChALkeR
Copy link
Member

ChALkeR commented Dec 19, 2015

There was never a CI run for this, right?

See #4336 (comment)

@jasnell
Copy link
Member

jasnell commented Dec 19, 2015

Entirely possible.
On Dec 19, 2015 5:00 AM, "Сковорода Никита Андреевич" <
notifications@github.com> wrote:

There was never a CI run for this, right?


Reply to this email directly or view it on GitHub
#3686 (comment).

@Fishrock123
Copy link
Contributor

@ChALkeR CI runs are mostly useless for these, except to see if it clones I guess.

@MylesBorins
Copy link
Contributor

should we have an npm CI run that run make test-npm

I should be able to spin that up on jenkins pretty quickly

othiym23 added a commit that referenced this pull request Dec 23, 2015
Dependency upgrades.

PR-URL: #3686
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
@Fishrock123
Copy link
Contributor

@thealphanerd For 2.x it needs to do sudo make install first though.

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.

5 participants