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 v7.20.0 #3550

Merged
merged 27 commits into from Jul 15, 2021
Merged

Release v7.20.0 #3550

merged 27 commits into from Jul 15, 2021

Conversation

ruyadorno
Copy link
Collaborator

v7.20.0 (2021-07-15)

FEATURES

BUG FIXES

DOCUMENTATION

DEPENDENCIES

  • 691816f3d @npmcli/arborist@2.7.1
    • fixes running prepare scripts for workspaces on reify
    • ensure pacote always compares correct integrity values
  • b9597e944 make-fetch-happen@9.0.4
    • fix: retry socket timeout failures
    • fix: clean up invalid indexes and content after cacache read errors
  • f573e7c56 minipass-fetch@1.3.4
    • fix: correctly handle error events that happen after response events
  • 2d5797ea0 pacote@11.3.5
    • fix: show more actionable messages for git pathspec errors
    • fix: include all dep types when building for prepare
    • fix: do not set mtime when unpacking

wraithgar and others added 27 commits July 1, 2021 11:19
"on install" was ambiguous because it wasn't clear if it meant "when npm
install is ran on this project" or "when this project is installed
somewhere else"

PR-URL: #3491
Credit: @wraithgar
Close: #3491
Reviewed-by: @ljharb
Adds an example of when `npm update` would not install the latest
version of a package because other subdependencies in your tree have
tighter restrictions.

PR-URL: #3494
Credit: @wraithgar
Close: #3494
Reviewed-by: @lukekarrys
Implements `npm pkg get|set|delete` support. It enables retrieving and
modifying values in a `package.json` file of any given project.

Included are the implementation based on npm/rfcs#402
along with extensive tests and user documentation.

Relates to: npm/rfcs#402
Fixes: npm/statusboard#368

PR-URL: #3487
Credit: @ruyadorno
Close: #3487
Reviewed-by: @wraithgar
The flattener worked for everything except for when you are using
`npm config set` itself.  Now it works for both.

PR-URL: #3508
Credit: @wraithgar
Close: #3508
Reviewed-by: @nlf
This looks very wrong on white terminals.

npmlog still makes its `notice` logs do this but that will have to be
fixed in the npmlog repo.

PR-URL: #3499
Credit: @wraithgar
Close: #3499
Reviewed-by: @nlf
This adds the `audit` config item to the usage output of `npm ci`, and
also tweaks how usage flags are shown for boolean options that do not
default to false.  Their usage is shown as the `--no-x` form of the flag
to better communicate that the flag is needed to turn that normally true
option OFF.

The description of `audit` was also updated to reflect that it runs on
many different npm commands, not just install.  Because this flag is
included in the usage of those commands it's best to let the assocation
happen there instead of trying to be comprehensive in the description
itself.

A small fix to make `install-ci-test` not try to redefine its own
usage, but to inherit from `ci` was also included.

PR-URL: #3497
Credit: @wraithgar
Close: #3497
Reviewed-by: @nlf
It will be helpful to us when debugging the "exit handler never called"
bugs to know which timings were started but not ended.

Tests moved to use real npm.

PR-URL: #3479
Credit: @wraithgar
Close: #3479
Reviewed-by: @ruyadorno
 * npm mock logger writes to npm.log.record too now
 * No more extra process.exit from within the process `exit` event handle.
 * No more `exit()` function.  Logic is rolled up into the exit handler.
 * Now there is only an exit handler and an exit event listener.
   `lib/utils/perf.js` was rolled up into npm.js itself.

Unfortunately the tests were written in such a way that any further
refactoring of the exit handler was going to require also rewriting the
tests.  Fortunately NOW the tests are interacting with the exit handler
in a way that shouldn't require them to be rewritten AGAIN if we change
the internals of the exit handler.

PR-URL: #3482
Credit: @wraithgar
Close: #3482
Reviewed-by: @nlf
Two files got into node_modules in a way that changes if you are on a
system that is case sensitive. One was a readme that is now properly
being ignored, the other is a typescript file that is upper case in some
instances

PR-URL: #3540
Credit: @wraithgar
Close: #3540
Reviewed-by: @ruyadorno
* nodejs -> Node.js
* javascript -> JavaScript

PR-URL: #3542
Credit: @relrelb
Close: #3542
Reviewed-by: @wraithgar
Adds ability to using empty bracket syntax as a shortcut to appending
items to the end of an array when using `npm pkg set`, e.g:

npm pkg set keywords[]=foo

Relates to: npm/rfcs#402

PR-URL: #3539
Credit: @ruyadorno
Close: #3539
Reviewed-by: @darcyclarke, @ljharb
Currently, the name: `npm-robot` is being used in nodejs changelogs as
the atttribution author name for npm-update commits. This makes it so
that entries in the changelog referring to our updates reads like:

```
upgrade npm to 7.18.1 (npm-robot) #39065
```

This change makes it so that the name used in commits is `npm team`,
this way the changelogs entry should read instead as:

```
upgrade npm to 7.18.1 (npm team) #39065
```

Ref: https://nodejs.org/en/blog/release/v16.4.0/

PR-URL: #3541
Credit: @ruyadorno
Close: #3541
Reviewed-by: @wraithgar, @targos, @BethGriggs
@ruyadorno ruyadorno requested a review from a team as a code owner July 15, 2021 19:37
@ruyadorno ruyadorno changed the title Release/v7.20.0 Release v7.20.0 Jul 15, 2021
@ruyadorno ruyadorno merged commit 1a2159d into latest Jul 15, 2021
@nlf nlf deleted the release/v7.20.0 branch March 28, 2022 20:48
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

5 participants