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.8.0 #3017

Merged
merged 12 commits into from
Apr 1, 2021
Merged

release/v7.8.0 #3017

merged 12 commits into from
Apr 1, 2021

Conversation

wraithgar
Copy link
Member

@wraithgar wraithgar commented Apr 1, 2021

v7.8.0 (2021-04-01)

FEATURES

BUG FIXES

DEPENDENCIES

  • 61da39beb @npmcli/config@2.1.0
    • feat(config): add support for envExport:false
  • fb095a708 @npmcli/arborist@2.3.0:
    • #2896 Provide currentEdge in ERESOLVE if known, and address self-linking edge case.
    • Add/remove dependencies to/from workspaces when set, not root project
    • Only reify the portions of the dependency graph identified by the workspace configuration value.
    • Do not recursively chown the project root path.

wraithgar and others added 10 commits March 31, 2021 13:58
This adds workspaces support to `npm repo` and `npm docs`.

It also updates the usage output to support the -w and -ws parameters
output, and cleans up some unneccessary functions in `run-script` and
`exec`.

PR-URL: #2972
Credit: @wraithgar
Close: #2972
Reviewed-by: @nlf
Implements workspaces for set-script, also refactors tests to mock as
little as possible.

PR-URL: #2998
Credit: @nlf
Close: #2998
Reviewed-by: @wraithgar
PR-URL: #3001
Credit: @wraithgar
Close: #3001
Reviewed-by: @nlf
This got left out of the npm view workspaces PR
It defaults to true, but setting it to any falsey value will tell
`@npmcli/config` not to export it into the environment, and will also
put a remark in the documentation that it is not exported.

PR-URL: #3014
Credit: @isaacs
Close: #3014
Reviewed-by: @nlf
* [#2896](#2896) Provide currentEdge in
  ERESOLVE if known, and address self-linking edge case.
* Add/remove dependencies to/from workspaces when set, not root project
* Only reify the portions of the dependency graph identified by the
  `workspace` configuration value.
* Do not recursively `chown` the project root path.
If a user runs 'npm install -w foo bar baz', that won't set 'bar' and
'baz' as workspace names.  The correct incantation is 'npm install -w
foo -w bar -w baz'.

PR-URL: #3016
Credit: @isaacs
Close: #3016
Reviewed-by: @wraithgar
Adds workspaces configuration to `docs`, `repo`, and `set-script`.

PR-URL: #3013
Credit: @wraithgar
Close: #3013
Reviewed-by: @darcyclarke
While it is somewhat helpful to get reports on this, since it indicates
an underlying problem in Arborist, it's also very disruptive and
unhelpful for users.  As of 2.3.0, Arborist gives us the currentEdge if
available, so we _can_ report on that at least.  If there is no node
_or_ edge, then we just don't say what the current state is, which isn't
useful, but at least is less annoying than a 'property of null'
exception.

PR-URL: #3015
Credit: @isaacs
Close: #3015
Reviewed-by: @wraithgar
@wraithgar wraithgar requested a review from a team as a code owner April 1, 2021 19:51
@wraithgar wraithgar changed the title Release next release/v7.8.0 Apr 1, 2021
@wraithgar wraithgar merged commit dedb9c8 into latest Apr 1, 2021
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.

3 participants