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.0.8 #2115

Merged
merged 21 commits into from Nov 3, 2020
Merged

Release/v7.0.8 #2115

merged 21 commits into from Nov 3, 2020

Conversation

isaacs
Copy link
Contributor

@isaacs isaacs commented Nov 3, 2020

7.0.8 (2020-11-03)

DOCUMENTATION

BUG FIXES

  • 6cd3cd08a Support all conf keys in publishConfig
  • a1f9be8a7 #2074 Support publishing any kind of spec, not just directories

DEPENDENCIES

  • 545382df6 libnpmpublish@4.0.0:
    • Support publishing things other than folders
  • 7d88f1719 npm-registry-fetch@9.0.0
  • 823b40a4e pacote@11.1.12
  • 90bf57826 npm-profile@5.0.2
  • e5a413577 libnpmteam@2.0.2
  • fc5aa7b4a libnpmsearch@3.0.1
  • 9fc1dee13 libnpmorg@2.0.1
  • 0ea870ec5 libnpmhook@6.0.1
  • 32fd744ea libnpmaccess@4.0.1
  • fc76f3d9f @npmcli/arborist@1.0.8
    • Fix cannot read property 'description' of undefined in npm ls when package-lock.json is corrupted
    • Do not allow peerDependencies to be nested under dependents in any circumstances
    • Always resolve peerDependencies in --prefer-dedupe mode

foxxyz and others added 17 commits November 3, 2020 14:26
updated usage from: https://github.com/npm/cli/blob/v7.0.1/lib/exec.js#L8-L20,
and removed extra `-p` occurrences to avoid confusion.

Credit: @dr-js
Close: #1970
Reviewed-by: @ruyadorno
This adds a flatOptions.flatten() method, which takes an object full of
config keys, and turns it into an options object.  This method expects
an object that already inherits from npm's defaults, and is thus
expected to be internal only.

This commit also removes some config keys which were used by npm
dependencies at the start of the v7 beta process, but are no longer:

- all lockfile configs (since we don't use lockfiles any more! for
  anything! and good riddance, they're a rats' nest of race conditions)
- cacheMax/cacheMin (we only use preferOffline/offline/online now, so
  these are strictly legacy support as input and never shared with deps)

Once this lands in cli, we can remove the publishConfig handling logic
in npm-registry-fetch, as it will be redundant.
Support publishing things other than folders
This causes a lot of duplicates which will be removed in subsequent
commits.
Less manual effort paper cuts.
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

4 participants