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.5.3 #2626

Merged
merged 18 commits into from Feb 8, 2021
Merged

Release/v7.5.3 #2626

merged 18 commits into from Feb 8, 2021

Conversation

ruyadorno
Copy link
Collaborator

@ruyadorno ruyadorno commented Feb 4, 2021

v7.5.3 (2021-02-08)

BUG FIXES

DEPENDENCIES

  • 3294fed6f pacote@11.2.5
    • prevent infinite recursion in git dep preparation
  • 0f7a3a87c read-package-json-fast@2.0.1
    • avoid duplicating optionalDependencies as dependencies in package.json
  • 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

@ruyadorno
Copy link
Collaborator Author

ah 😅 we should def cut a release of read-package-json-fast and update it here too

nlf and others added 7 commits February 5, 2021 09:43
- 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
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.
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

3 participants