Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm skipping the release train and violating npm's release process a little, because the major new "feature" of
npm@2.5.1
is that its tests have been updated to pass on io.js 1.1.x (see #663 for context). The test failures weren't always visible because thetest-npm
stanza in the Makefile needs to be updated to ensure that the PATH is set up to only run the binary built by the Makefile. Forjoyent/node
, the patch looks like:But for io.js, it's more complicated, because npm's tests themselves rely upon the
node
binary being present, and that's not guaranteed in the cases where thenode
→iojs
symlink might not have been made yet.These test changes complement
npm@2.5.0
, which includes a small new feature (see below), but more important fixes a potentially serious regression innpm-registry-client
that would causenpm@2.3.0
andnpm@2.4.1
to have issues connecting to registries from within proxied networks (which would also prevent using the bundled npm to update itself if these environments).The shorter changelog is:
0e8d473
#7281npm-registry-mock@1.0.0
: Clean up API, setconnection: close
, which makes tests pass on io.js 1.1.x.(@robertkowalski)
f9313a0
#7226 Ensure that all request
settings are copied onto the agent.
(@othiym23)
fec4c96
Allow
--no-proxy
to overrideHTTP_PROXY
setting in environment.(@othiym23)
9d61e96
npm outdated --long
now includes a column showing the type of dependency.(@watilde)
NOTE: skipping ahead in the release train probably means there won't be a new PR for npm being updated next week.