Skip to content

Conversation

@zkat
Copy link
Contributor

@zkatzkat commented Aug 15, 2018

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
Where this should land
  • Node 10
  • Node 8
Notable Changes

This release includes two versions of npm, including the current latest release, [email protected].

  • f861c2b57[email protected]: This means our entire npm dep tree now uses the latest node-gyp, and we've updated and flattened request as well. npm audit on npm itself comes up clean now! (@rvagg)

  • 6e9f04b0bnpm/cli#8 Search for authentication token defined by environment variables by preventing the translation layer from env variable to npm option from breaking :_authToken. (@mkhl)

  • 84bfd23e7npm/cli#35 Stop filtering out non-IPv4 addresses from local-addrs, making npm actually use IPv6 addresses when it must. (@valentin2105)

  • d81146181npm/cli#32 Don't check for updates to npm when we are updating npm itself. (@olore)

  • Another reminder that we've moved our issue tracking! You can read more about our move away from GitHub for issue tracking on our blog

Changelogs

@nodejs-github-botnodejs-github-bot added the npm Issues and PRs related to the npm client dependency or the npm registry. label Aug 15, 2018
@brody4hire
Copy link

I would like to thank @zkat, @rvagg, and others for the dedication behind this nice update. I suspect you already know that we will have to wait a couple weeks for this one to land ref:

@zkat
Copy link
ContributorAuthor

zkat commented Aug 16, 2018

Yes, I'm aware of the policy, seeing as I was part of the discussion for it. :)

Copy link
Member

@BridgeARBridgeAR left a comment

Choose a reason for hiding this comment

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

RSLGTM

@joyeecheung
Copy link
Member

This PR needs a rebase against master to avoid the git failure in the CI.

@BridgeAR
Copy link
Member

@joyeecheung would it not be sufficient to rebase on the CI task?

@zkat
Copy link
ContributorAuthor

zkat commented Aug 22, 2018

I've rebased it 👍

@zkatzkat mentioned this pull request Aug 29, 2018
4 tasks
@zkat
Copy link
ContributorAuthor

zkat commented Aug 29, 2018

Moving this to #22591, since 6.4.1 came out in the meantime 😅

@zkatzkat closed this Aug 29, 2018
@brody4hire
Copy link

Doesn't that mean we have to wait another 2 weeks to get [email protected] integrated?

@wraithgarwraithgar deleted the npm-6.4.0 branch June 26, 2025 15:41
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

npmIssues 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

@zkat@brody4hire@BridgeAR@joyeecheung@nodejs-github-bot