-
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.5.3 #2626
Merged
Merged
Release/v7.5.3 #2626
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
9ba70c0
to
119c957
Compare
wraithgar
approved these changes
Feb 4, 2021
ah 😅 we should def cut a release of read-package-json-fast and update it here too |
- remove spawn util, refactor help command - add tests for read-user-info, minor refactor - add tests for pulse-till-done util, refactor - add tests for otplease util - add tests for open-url util - remove unused no-progress-while-running util PR-URL: #2601 Credit: @nlf Close: #2601 Reviewed-by: @ruyadorno, @wraithgar
The "do you have auth configured" only takes into consideration a hard-coded "registry" config, which means that if you don't have auth configured for the npm registry, but you do for the one you have tied to a scope elsewhere in your npmrc, we would erroneously tell you that to add a token. This uses the same method that the rest of the publish chain uses to determine which registry it would be publishing to, then sees if you have auth for THAT registry. Because that other function does a hard fallback to the npm registry, there is no more need for the exception we throw if you do not have one configured. Also, the npm cli already defaults that config item, so you can't even set it to a falsey value if you wanted
PR-URL: #2613 Credit: @nlf Close: #2613 Reviewed-by: @ljharb, @wraithgar
119c957
to
924879f
Compare
Fixes a compatibility issue in `npm ls` due to the subtle internal change of optional dependencies being pruned from dependencies in `read-package-json-fast@2.0.0` update.
924879f
to
b976282
Compare
b976282
to
e815cd4
Compare
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.5.3 (2021-02-08)
BUG FIXES
df596bf4c
fix(publish): follow all configs for registry auth check #2602 (@wraithgar)6d7afb03c
#2613 install script: pass -q to curl calls to disable user .curlrc files (@nlf)DEPENDENCIES
3294fed6f
pacote@11.2.5
0f7a3a87c
read-package-json-fast@2.0.1
6f46b0f7f
init-package-json@2.0.2
df4f65acc
@npmcli/arborist@2.2.0
7038c2ff4
@npmcli/run-script@1.8.2
54cd4c87a
libnpmversion@1.0.8
9ab36aae4
graceful-fs@4.2.5
e1822cf27
@npmcli/installed-package-contents@1.0.7