-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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.0.15 #2252
Merged
Merged
Release/v7.0.15 #2252
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
replace obsolete doc about root-privilege with changelog notes @ https://github.com/npm/cli/blob/e1a2837809a76896523cdfcbce7537e46f71d67e/CHANGELOG.md#v700-beta0-2020-08-04 PR-URL: #2196 Credit: @kaizhu256 Close: #2196 Reviewed-by: @darcyclarke
line 435: aknowledging->acknowledging line 1099: overwhich -> over which PR-URL: #2200 Credit: @alexwoollam Close: #2200 Reviewed-by: @darcyclarke
Fixes two issues that enable running tests downstream in nodejs: - Running tests using `npm run-script test` instead of the `npm test` alias will result in a failure since `test/lib/npm.js` have an assertion for "test" being the command only. This changes it so that this particular test also accepts "run-script" as the command. - Explicitly enable colors for tap output so that running the test suite in a non-tty environment will result in output that matches coloured snapshots. PR-URL: #2225 Credit: @ruyadorno Close: #2225 Reviewed-by: @darcyclarke
PR-URL: #2238 Credit: @d-fischer Close: #2238 Reviewed-by: @ruyadorno
PR-URL: #2240 Credit: @ruyadorno Close: #2240 Reviewed-by: @darcyclarke
Fix: npm/statusboard#245 Fix: npm/statusboard#246 PR-URL: #2241 Credit: @ruyadorno Close: #2241 Reviewed-by: @darcyclarke
Fixes: npm/statusboard#166 PR-URL: #2244 Credit: @ruyadorno Close: #2244 Reviewed-by: @darcyclarke
When running `npm link <pkg>` it should not save the new item to the currrent dependencies of that package.json file. Fixes: #2034 Co-authored-by: Darcy Clarke <[email protected]> PR-URL: #2245 Credit: @ruyadorno Close: #2245 Reviewed-by: @darcyclarke
Thank you for your hard work, what a great release 👍 |
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.
7.0.15 (2020-11-27)
DEPENDENCIES
00e6028ef
@npmcli/[email protected]
package.json
BUG FIXES
9c3413fbc
#2034 #2245npm link <pkg>
should not savepackage.json
(@ruyadorno)DOCUMENTATION
1875347f9
#2196 remove doc on obsoleteunsafe-perm
flag (@kaizhu256)f51e50603
#2200config.md
cleanup (@alexwoollam)997cbdb40
#2238 Fix broken link topackage.json
documentation (@d-fischer)9da972dc4
#2241npm star
docs cleanup (@ruyadorno)