npm-registry-client@2.0.3
1.4.21
Don't squash execute perms in _git-remotes/ dir

A previous fix for https://github.com/npm/npm/issues/3117
explicitly set the permissions for all files to a hard-coded
value, regardless of what the permissions were previously.

This changes that behavior to *add* the permissions that were
previously being *set* so that existing execute permissions are
maintained.

This is a redo of the much more blunt solution attempted in
https://github.com/npm/npm/pull/5728
thanks to some very helpful feedback from @othiym23
Bump semver to version 3

This makes the '^' operator stricter for 0.x.y versions, even if 'x' is
not 0.

As a direct result, several *other* deps had to be updated, because they
either depended on semver 2.x, or because the new stricter rules meant
that they (or their deps) were no longer valid.

The update to 'read-installed', in particular, causes a test failure.
That update must be rolled back, or the test made to pass, prior to a
stable npm 2.0.0 release going out.
init-package-json@1.0.0

Defaults package versions in 'npm init' to 1.0.0 instead of 0.0.0
license: Cleaned up legalese with actual lawyer
cmd-shim@1.1.2
glob@4.0.5
fstream@0.1.29
github-url-from-git@1.2.0
read-package-json@1.2.4
v1.4.22
update several dependencies

The quest to avoid SemVer '0.x' magic continues.
v1.4.23
merge v1.4
Add a test to verify that 'npm ls' exits ok in npm repo
remove unnecessary mkdirps
read-installed@3.0.0

Fixes extraneous peer dependent looping devDependencies in --production mode.

CC @davglass
move fetch into npm-registry-client

The primary purpose is so that everything doing network requests
includes auth, if so required. Sends bearer token by default, will send
HTTP Basic auth with `always-auth` set in the config.
2.0.0-alpha.6.0