v7.1.1 proposal

[rvagg]

This is the changelog, with a novel notice that we don't normally include:

v7.1.1 2020-10-15

This release restores the location of shared library builds to the pre-v7
location. In v7.0.0 until this release, shared library outputs were placed
in a lib.target subdirectory inside the build/{Release,Debug} directory for
builds using make (Linux, etc.). This is inconsistent with macOS (Xcode)
behavior and previous node-gyp behavior so has been reverted.
We consider this a bug-fix rather than semver-major change.

• [ee6a837cb7] - gyp: update gyp to 0.6.1 (Rod Vagg) #2238
• [3e7f8ccafc] - lib: better log message when ps fails (Martin Midtgaard) #2229
• [7fb314339f] - test: GitHub Actions: Test on Python 3.9 (Christian Clauss) #2230
• [754996b9ec] - doc: replace status badges with new Actions badge (Rod Vagg) #2218
• [2317dc400c] - ci: switch to GitHub Actions (Shelley Vohr) #2210
• [2cca9b74f7] - doc: drop the --production flag for installing windows-build-tools (DeeDeeG) #2206

[rvagg]

It looks like we've got out of sync with npm dependencies again (as expected I suppose).

nopt is at 4.0.3, while npm has 5.0.0
rimraf is at 2.0.2, while npm is at 3.0.0
tar is at 6.0.1, npm has 6.0.5 but we're both doing ^ and we don't bundle a package-lock so that should be OK

@MylesBorins it seems you're the right person to address this to now. Would you like to delay this release a little more to get this sorted out to offer additional de-dupe, or do that after release. We also still need to tackle our deprecated request dependency as well, that might be next one our list of big items for a node-gyp release. @imatlopez has been helping with options for that, with an initial attempt in #2220.

[MylesBorins]

If nopt + rimraf could easily be updated that sounds like it would benefit everyone (smaller tarball sizes)

That said we are cutting it close to 15.0.0, and we can always cut new versions and iterate quickly.

I think if updating deps are going to delay by days, rather than hours, we should punt

[rvagg]

let's get deps update in, it's pretty simple #2240, I can cut a new release as soon as I get a 👍 from a regular team member or two

[rvagg]

done and published, with updated deps, oty @MylesBorins