Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release/v8.1.4 #4066

Merged
merged 25 commits into from Nov 18, 2021
Merged

Release/v8.1.4 #4066

merged 25 commits into from Nov 18, 2021

Conversation

fritzy
Copy link
Contributor

@fritzy fritzy commented Nov 18, 2021

v8.1.4 (2021-11-18)

BUG FIXES

DEPENDENCIES

wraithgar and others added 25 commits November 4, 2021 14:45
This brings us in line with the rest of the linting rules we are wanting
to use on the npm cli repos.

There were several hundred over-length lines and instead of editing them
all by hand I piped the failing file through `prettier` and back through
`eslint` just to save some time and energy.  This means there may be
some quirks in the linting those files have, but we can fix those if we
see them and they bother us.

Other than that there were about 50 lines that are legitimately
over-length, all are now explicitly overridden.  Many are tests that
could be snapshots.

PR-URL: #3995
Credit: @wraithgar
Close: #3995
Reviewed-by: @lukekarrys
* Update to eslint@8 and and @npmcli/eslint-config@2.0.0
* Remove eslint-plugin-node.

Also remove an unused script that was failing linting.  We don't use the
update-dist-tags script anymore as part of our release process.

PR-URL: #4016
Credit: @wraithgar
Close: #4016
Reviewed-by: @lukekarrys
Uses the real npm object and doesn't mock anything.

PR-URL: #4018
Credit: @wraithgar
Close: #4018
Reviewed-by: @lukekarrys
These are never valid in the contexts from which this lib is called.
Namely these are the bugs, docs, fund, help, and repo commands, and for
oauth logins.

PR-URL: #4025
Credit: @wraithgar
Close: #4025
Reviewed-by: @isaacs
Clean up tests too

PR-URL: #4033
Credit: @wraithgar
Close: #4033
Reviewed-by: @lukekarrys
Looks like tests were removed but the snapshots still have them.

PR-URL: #4019
Credit: @wraithgar
Close: #4019
Reviewed-by: @lukekarrys
The fake npm object in the tests wasn't returning an async function

Fixes: #4020

PR-URL: #4032
Credit: @wraithgar
Close: #4032
Reviewed-by: @lukekarrys
During a refactoring of the tests a bug was found in the install command
completion that would return nothing if there was a valid match, this
fixes that bug and also makes the tests actually test things.

PR-URL: #4023
Credit: @wraithgar
Close: #4023
Reviewed-by: @lukekarrys
now that we're off of node10 we can clean this up

PR-URL: #3989
Credit: @wraithgar
Close: #3989
Reviewed-by: @lukekarrys
Use a real npm object, actually assert things

PR-URL: #4036
Credit: @wraithgar
Close: #4036
Reviewed-by: @lukekarrys
 * When rendering HTML documentation, don't use smart quotes because they're icky and hard to copy/paste.
 * Add a <!DOCTYPE html> and a <meta charset="utf-8"> to be good HTML citizens.

PR-URL: #4046
Credit: @ethomson
Close: #4046
Reviewed-by: @wraithgar
PR-URL: #4050
Credit: @fritzy
Close: #4050
Reviewed-by: @wraithgar

PR-URL: #4050
Credit: @fritzy
Close: #4050
Reviewed-by: @wraithgar
PR-URL: #4049
Credit: @wraithgar
Close: #4049
Reviewed-by: @fritzy
PR-URL: #4048
Credit: @wraithgar
Close: #4048
Reviewed-by: @fritzy
 * feat: support vs2022
 * feat: build with config.gypi from node headers

PR-URL: #4045
Credit: @wraithgar
Close: #4045
Reviewed-by: @lukekarrys
PR-URL: #4065
Credit: @fritzy
Close: #4065
Reviewed-by: @lukekarrys
@fritzy fritzy requested a review from a team as a code owner November 18, 2021 20:39
@fritzy fritzy merged commit 940ba87 into latest Nov 18, 2021
@nlf nlf deleted the release/v8.1.4 branch March 28, 2022 20:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants