-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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.16.0 #3322
Closed
Closed
Release/v7.16.0 #3322
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I think this change was incorrect: #2024 The point of this example is that the same script is being used for two different stages (`install` and `post-install`) so it would be a good idea to look at the `npm_lifecycle_event` environment variable inside this script to determine which stage is being run. PR-URL: #3282 Credit: @KevinFCormier Close: #3282 Reviewed-by: @wraithgar
Change the output in `npm ls` for symlink dependencies (including workspaces) to show the relative path from the project root, rather than the absolute path of the link target. This makes the output much less noisy and more ergonomic when many workspaces and link dependencies are in use, especially when paths are long. It is arguable that this output might be slightly misleading, since the _actual_ workspace symlink from `${root}/node_modules/b` to `${root}/packages/b` has a link value of `../packages/b`, not just `packages/b`. (Or on Windows, always the full absolute path, because junctions.) Thus, `npm ls b` will not show the same output as `ls -l node_modules/b`. However, `npm ls` shows the logical tree, not the physical tree, so presenting the user with a path that they can use and interpret is more important than presenting them with the strictly accurate details of their filesystem. PR-URL: #3272 Credit: @isaacs Close: #3272 Reviewed-by: @darcyclarke
* fix(exit-code): account for null auditLevel default (#46)
PR-URL: #3304 Credit: @NariyasuHeseri Close: #3304 Reviewed-by: @wraithgar
PR-URL: #3307 Credit: @rethab Close: #3307 Reviewed-by: @wraithgar
When running 'npm audit', we properly exited correctly with the appropriate exitCode based on the audit level config and the report results. However, when going through the reifyFinish() function (as we do for 'npm audit fix'), we were not setting that properly if the auditLevel was not set. Furthermore, if the auditLevel WAS set, we were setting the exit code to non-zero for *other* reify commands (install, update, etc.), where the audit information should be strictly advisory. When --json and --loglevel=silent were set, the exitCode was never being set properly. This fixes all these problems. PR-URL: #3311 Credit: @isaacs Close: #3311 Reviewed-by: @wraithgar
PR-URL: #3312 Credit: @isaacs Close: #3312 Reviewed-by: @wraithgar
PR-URL: #3313 Credit: @spencerwilson Close: #3313 Reviewed-by: @wraithgar
Allow users to publish all workspaces with `npm publish --ws` while also skipping any workspace that might have been intentionally marked as private, using `"private": true` in its package.json file. Fixes: #3268 PR-URL: #3285 Credit: @ruyadorno Close: #3285 Reviewed-by: @wraithgar
* devDependency used for building html docs
0.9.0 does not work in node 10.1 so our CI fails
* feat: allow fully deleting indices * feat: add a validateEntry option to compact * chore: lint * chore: use standard npm style release scripts
Moves workflow to create NPM CLI dependency pull request from npm/node. Adds input to workflow dispatch trigger PR-URL: #3294 Credit: @gimli01 Close: #3294 Reviewed-by: @darcyclarke
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
v7.16.0 (2021-05-27)
FEATURES
399ff8cbc
#3312 feat(link): add workspace support (@isaacs)BUG FIXES
83590d40f
#3272 fix(ls): show relative paths from root (@isaacs)a574b518a
#3304 fix(completion): restore IFS even ifnpm completion
returns error (@NariyasuHeseri)554e8a5cd
#3311 set audit exit code properly (@isaacs)4a4fbe33c
#3268 #3285 fix(publish): skip private workspaces (@ruyadorno)DEPENDENCIES
7b56bfdf3
cacache@15.2.0
:dbbc151a3
npm-audit-report@2.1.5
:5b2604507
chore(package-lock): update devDependencies (@Gar)DOCUMENTATION
46a9bcbcb
#3282 fix(docs): proper postinstall script file name (@KevinFCormier)3c53d631f
#3307 fix(docs): typo in package-lock.json docs (@rethab)96367f93f
rebuild npm-pack doc (@isaacs)64b13dd10
#3313 Drop stale Python 3<->node-gyp remark (@spencerwilson)AUTOMATION
3d5df0082
#3294 chore(ci): move node release PR workflow into cli (@gimli01)