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: npm@6.10.1 #207

Merged
merged 19 commits into from Jul 3, 2019
Merged

Release: npm@6.10.1 #207

merged 19 commits into from Jul 3, 2019

Conversation

isaacs
Copy link
Contributor

@isaacs isaacs commented Jul 2, 2019

BUGFIXES

DEPENDENCIES

@isaacs isaacs requested a review from a team as a code owner July 2, 2019 22:21
@isaacs
Copy link
Contributor Author

isaacs commented Jul 2, 2019

SemVer v6 would be nice, but it'll require a lot of other modules to be updated. Most of the other outdated deps drop support for node 6, so they'll come in npm v7.

@isaacs isaacs added the release label Jul 2, 2019
isaacs and others added 19 commits July 3, 2019 10:08
When running an npm command from within a git environment, such as
installing or testing during a git rebase or bisect, these environment
variables will be passed to the child process, causing it to
fetch/checkout/etc in the root project instead of doing what the user
intends.

Strip them out so that they are not passed to the child process.

Also, remove git environs from the test environment, so that spawning
git in a test to set up a dummy repo doesn't mess with the main
project's git repository.  This enables adding `exec npm test` in a `git
rebase -i` list to run tests between commits.
This also updates make-fetch-happen, so it no longer requires the old
lru-cache.
Instead of creating a new set each time a new node gets visited, so that
its siblings do not have it in `seen`, just remove the node from the
original set right after all child nodes are visited.

See #76

Credit: @larsgw

PR-URL: #206
Close: #206
Reviewed-by: @isaacs
Credit: @raywu0123
PR-URL: #179
Close: #179
Reviewed-by: @isaacs
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