npmconf@1.1.1
npmconf: Float patch to remove 'scope' from config defs
config docs: add cafile
add verbose log when project config file is ignored
Consolidate color sniffing in config/log loading process
use chrisdickinson's actual docs instead.

This reverts commit ff5058d8e5797ebc53ed57398b0b81390bf6e2a2.
docs: document cafile config setting
npmconf@1.1.2
Use core.longpaths on win32 git - fixes #5525
Allow to build all the docs OOTB.

Since 1.4.10, the html docs are generated via the marked module. when
doing the usual "make" dance, the build process stops when attempting to
generate the first html doc complaining about a missing
node_modules/.bin/marked.

This patch is a quick'n'dirty copy-pasta of the treatment applied to
load the ronn module but applied to marked. When applied against the
1.4.13 tarball it allows -- at least in a works-for-me manner -- to
generate all the docs.
replace escape codes with ansicolors
make docs less aggressively
include utils/git.js in version
typo in lib/utils/git.js
v1.4.17
now working on v1.5.0
glob@4.0.3
bump nopt and npmconf

Fixes #5591

The root cause here is that a change from 022 (a number in octal literal
format) to '022' (a string) caused the string to later be interpreted as
a decimal number, making for some wacky umask values.

Solution is multipart.

First, use the actual process.umask() value from the user's environment.
This is almost certainly what they want anyway.

Second, validate all default values just like we do with user- supplied
values, rather than trusting them to never be wrong.  This would've
found the problem much sooner, while in dev.

This second part requires that we allow a value of null for 'path' type
args, allow 'undefined' for the 'local-address' config, and avoid
looking up a cafile of 'null', all of which are good hygenic things to
add defense-in-depth anyway.
relative URLS for working non-root registry URLS
don't publish as latest until ready