-
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/v8.3.0 #4150
Merged
Merged
Release/v8.3.0 #4150
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
PR-URL: #4116 Credit: @nlf Close: #4116 Reviewed-by: @wraithgar
* Fixes object property assignment bug in resolving package-locks with conflicts PR-URL: #4141 Credit: @wraithgar Close: #4141 Reviewed-by: @fritzy
Closes: #4128 This also refactors the logic for cleaning log files to use the `ignore` option from `glob` to not clean current log files instead of relying on updating the `logs-max` count. I also discovered a bug where we weren't cleaning log files written with the old naming convention, so this fixes that as well. PR-URL: #4134 Credit: @lukekarrys Close: #4134 Reviewed-by: @wraithgar
PR-URL: #4092 Credit: @nlf Close: #4092 Reviewed-by: @wraithgar
PR-URL: #4118 Credit: @felipeplets Close: #4118 Reviewed-by: @darcyclarke
PR-URL: #4142 Credit: @lukekarrys Close: #4142 Reviewed-by: @wraithgar
Closes: npm/statusboard#416 PR-URL: #4143 Credit: @lukekarrys Close: #4143 Reviewed-by: @wraithgar
PR-URL: #4144 Credit: @nlf Close: #4144 Reviewed-by: @wraithgar
PR-URL: #4145 Credit: @nlf Close: #4145 Reviewed-by: @wraithgar
Closes: npm/statusboard#417 If the file at `$NPM_CONFIG_PREFIX/package.json` contains a `publishConfig`, the key/value pairs will be printed along with the rest of the output from `npm config ls`. PR-URL: #4146 Credit: @lukekarrys Close: #4146 Reviewed-by: @nlf
found 1 benchmarks with statistically significant performance regressions
timing results
|
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.
v8.3.0 (2021-12-09)
Features
4b0c29a7c
#4116 feat:@npmcli/arborist@4.1.0
(@nlf)166d9e144
npm/statusboard#416 #4143 feat: output configured registry during publish (@lukekarrys)71777be17
npm/statusboard#417 #4146 feat: displaypublishConfig
duringconfig list
(@lukekarrys)Bug Fixes
08c663931
#4128 #4134 fix: dont warn on error cleaning individual log files (@lukekarrys)e605b128c
#4142 fix: redact all private keys from config output (@lukekarrys)Documentation
db1885d7f
#4092 chore(docs): document overrides (@nlf)Dependencies
e1da1fa4b
#4141 deps:@npmcli/arborist@4.1.1
:parse-conflict-json@2.0.1
conflicts
1d8bec566
#4144 #3884 deps:minipass@3.1.6