Release: npm@6.10.1 by isaacs · Pull Request #207 · npm/cli

isaacs · 2019-07-02T22:21:28Z

BUGFIXES

752e1837a#206 improve isOnly(Dev,Optional) (@larsgw)
970717c7b#179 fix-xmas-underline (@raywu0123)
e13afad99 fix(git): strip GIT environs when running git (@isaacs)

DEPENDENCIES

e7513eafalru-cache@5.1.1 (@isaacs)
ae4ff9e88npm-registry-fetch@3.9.1: (@isaacs)
e091b767ccall-limit@1.1.1 (@isaacs)
e25e2b292glob@7.1.4 (@isaacs)
c40ca2d76inherits@2.0.4 (@isaacs)
f00a74293libnpmsearch@2.0.1 (@isaacs)
8757f67d3marked@0.6.3 (@isaacs)
633befeddmarked-man@0.6.0 (@isaacs)
b2e98a343npm-lifecycle@2.1.1 (@isaacs)
e69537dcenode-gyp@4.0.0 (@isaacs)
23e8b9410query-string@6.8.1 (@isaacs)
572eaffcbtar-stream@2.1.0 (@isaacs)
609f62f31worker-farm@1.7.0 (@isaacs)
3e9891181readable-stream@3.4.0 (@isaacs)

isaacs · 2019-07-02T22:24:32Z

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.

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.

@larsgw

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: #206Close: #206 Reviewed-by: @isaacs

@raywu0123

Credit: @raywu0123 PR-URL: #179Close: #179 Reviewed-by: @isaacs

isaacs · 2019-07-02T22:21:28Z

BUGFIXES

752e1837a#206 improve isOnly(Dev,Optional) (@larsgw)
970717c7b#179 fix-xmas-underline (@raywu0123)
e13afad99 fix(git): strip GIT environs when running git (@isaacs)

DEPENDENCIES

e7513eafalru-cache@5.1.1 (@isaacs)
ae4ff9e88npm-registry-fetch@3.9.1: (@isaacs)
e091b767ccall-limit@1.1.1 (@isaacs)
e25e2b292glob@7.1.4 (@isaacs)
c40ca2d76inherits@2.0.4 (@isaacs)
f00a74293libnpmsearch@2.0.1 (@isaacs)
8757f67d3marked@0.6.3 (@isaacs)
633befeddmarked-man@0.6.0 (@isaacs)
b2e98a343npm-lifecycle@2.1.1 (@isaacs)
e69537dcenode-gyp@4.0.0 (@isaacs)
23e8b9410query-string@6.8.1 (@isaacs)
572eaffcbtar-stream@2.1.0 (@isaacs)
609f62f31worker-farm@1.7.0 (@isaacs)
3e9891181readable-stream@3.4.0 (@isaacs)

isaacs · 2019-07-02T22:24:32Z

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.

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.

@larsgw

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: #206Close: #206 Reviewed-by: @isaacs

@raywu0123

Credit: @raywu0123 PR-URL: #179Close: #179 Reviewed-by: @isaacs

isaacs · 2019-07-02T22:21:28Z

BUGFIXES

752e1837a#206 improve isOnly(Dev,Optional) (@larsgw)
970717c7b#179 fix-xmas-underline (@raywu0123)
e13afad99 fix(git): strip GIT environs when running git (@isaacs)

DEPENDENCIES

e7513eafalru-cache@5.1.1 (@isaacs)
ae4ff9e88npm-registry-fetch@3.9.1: (@isaacs)
e091b767ccall-limit@1.1.1 (@isaacs)
e25e2b292glob@7.1.4 (@isaacs)
c40ca2d76inherits@2.0.4 (@isaacs)
f00a74293libnpmsearch@2.0.1 (@isaacs)
8757f67d3marked@0.6.3 (@isaacs)
633befeddmarked-man@0.6.0 (@isaacs)
b2e98a343npm-lifecycle@2.1.1 (@isaacs)
e69537dcenode-gyp@4.0.0 (@isaacs)
23e8b9410query-string@6.8.1 (@isaacs)
572eaffcbtar-stream@2.1.0 (@isaacs)
609f62f31worker-farm@1.7.0 (@isaacs)
3e9891181readable-stream@3.4.0 (@isaacs)

isaacs · 2019-07-02T22:24:32Z

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.

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.

@larsgw

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: #206Close: #206 Reviewed-by: @isaacs

@raywu0123

Credit: @raywu0123 PR-URL: #179Close: #179 Reviewed-by: @isaacs

isaacs · 2019-07-02T22:21:28Z

BUGFIXES

752e1837a#206 improve isOnly(Dev,Optional) (@larsgw)
970717c7b#179 fix-xmas-underline (@raywu0123)
e13afad99 fix(git): strip GIT environs when running git (@isaacs)

DEPENDENCIES

e7513eafalru-cache@5.1.1 (@isaacs)
ae4ff9e88npm-registry-fetch@3.9.1: (@isaacs)
e091b767ccall-limit@1.1.1 (@isaacs)
e25e2b292glob@7.1.4 (@isaacs)
c40ca2d76inherits@2.0.4 (@isaacs)
f00a74293libnpmsearch@2.0.1 (@isaacs)
8757f67d3marked@0.6.3 (@isaacs)
633befeddmarked-man@0.6.0 (@isaacs)
b2e98a343npm-lifecycle@2.1.1 (@isaacs)
e69537dcenode-gyp@4.0.0 (@isaacs)
23e8b9410query-string@6.8.1 (@isaacs)
572eaffcbtar-stream@2.1.0 (@isaacs)
609f62f31worker-farm@1.7.0 (@isaacs)
3e9891181readable-stream@3.4.0 (@isaacs)

isaacs · 2019-07-02T22:24:32Z

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.

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.

@larsgw

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: #206Close: #206 Reviewed-by: @isaacs

@raywu0123

Credit: @raywu0123 PR-URL: #179Close: #179 Reviewed-by: @isaacs

isaacs · 2019-07-02T22:21:28Z

BUGFIXES

752e1837a#206 improve isOnly(Dev,Optional) (@larsgw)
970717c7b#179 fix-xmas-underline (@raywu0123)
e13afad99 fix(git): strip GIT environs when running git (@isaacs)

DEPENDENCIES

e7513eafalru-cache@5.1.1 (@isaacs)
ae4ff9e88npm-registry-fetch@3.9.1: (@isaacs)
e091b767ccall-limit@1.1.1 (@isaacs)
e25e2b292glob@7.1.4 (@isaacs)
c40ca2d76inherits@2.0.4 (@isaacs)
f00a74293libnpmsearch@2.0.1 (@isaacs)
8757f67d3marked@0.6.3 (@isaacs)
633befeddmarked-man@0.6.0 (@isaacs)
b2e98a343npm-lifecycle@2.1.1 (@isaacs)
e69537dcenode-gyp@4.0.0 (@isaacs)
23e8b9410query-string@6.8.1 (@isaacs)
572eaffcbtar-stream@2.1.0 (@isaacs)
609f62f31worker-farm@1.7.0 (@isaacs)
3e9891181readable-stream@3.4.0 (@isaacs)

isaacs · 2019-07-02T22:24:32Z

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.

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.

@larsgw

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: #206Close: #206 Reviewed-by: @isaacs

@raywu0123

Credit: @raywu0123 PR-URL: #179Close: #179 Reviewed-by: @isaacs

isaacs · 2019-07-02T22:21:28Z

BUGFIXES

752e1837a#206 improve isOnly(Dev,Optional) (@larsgw)
970717c7b#179 fix-xmas-underline (@raywu0123)
e13afad99 fix(git): strip GIT environs when running git (@isaacs)

DEPENDENCIES

e7513eafalru-cache@5.1.1 (@isaacs)
ae4ff9e88npm-registry-fetch@3.9.1: (@isaacs)
e091b767ccall-limit@1.1.1 (@isaacs)
e25e2b292glob@7.1.4 (@isaacs)
c40ca2d76inherits@2.0.4 (@isaacs)
f00a74293libnpmsearch@2.0.1 (@isaacs)
8757f67d3marked@0.6.3 (@isaacs)
633befeddmarked-man@0.6.0 (@isaacs)
b2e98a343npm-lifecycle@2.1.1 (@isaacs)
e69537dcenode-gyp@4.0.0 (@isaacs)
23e8b9410query-string@6.8.1 (@isaacs)
572eaffcbtar-stream@2.1.0 (@isaacs)
609f62f31worker-farm@1.7.0 (@isaacs)
3e9891181readable-stream@3.4.0 (@isaacs)

isaacs · 2019-07-02T22:24:32Z

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.

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.

@larsgw

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: #206Close: #206 Reviewed-by: @isaacs

@raywu0123

Credit: @raywu0123 PR-URL: #179Close: #179 Reviewed-by: @isaacs

isaacs · 2019-07-02T22:21:28Z

BUGFIXES

752e1837a#206 improve isOnly(Dev,Optional) (@larsgw)
970717c7b#179 fix-xmas-underline (@raywu0123)
e13afad99 fix(git): strip GIT environs when running git (@isaacs)

DEPENDENCIES

e7513eafalru-cache@5.1.1 (@isaacs)
ae4ff9e88npm-registry-fetch@3.9.1: (@isaacs)
e091b767ccall-limit@1.1.1 (@isaacs)
e25e2b292glob@7.1.4 (@isaacs)
c40ca2d76inherits@2.0.4 (@isaacs)
f00a74293libnpmsearch@2.0.1 (@isaacs)
8757f67d3marked@0.6.3 (@isaacs)
633befeddmarked-man@0.6.0 (@isaacs)
b2e98a343npm-lifecycle@2.1.1 (@isaacs)
e69537dcenode-gyp@4.0.0 (@isaacs)
23e8b9410query-string@6.8.1 (@isaacs)
572eaffcbtar-stream@2.1.0 (@isaacs)
609f62f31worker-farm@1.7.0 (@isaacs)
3e9891181readable-stream@3.4.0 (@isaacs)

isaacs · 2019-07-02T22:24:32Z

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.

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.

@larsgw

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: #206Close: #206 Reviewed-by: @isaacs

@raywu0123

Credit: @raywu0123 PR-URL: #179Close: #179 Reviewed-by: @isaacs

isaacs · 2019-07-02T22:21:28Z

BUGFIXES

752e1837a#206 improve isOnly(Dev,Optional) (@larsgw)
970717c7b#179 fix-xmas-underline (@raywu0123)
e13afad99 fix(git): strip GIT environs when running git (@isaacs)

DEPENDENCIES

e7513eafalru-cache@5.1.1 (@isaacs)
ae4ff9e88npm-registry-fetch@3.9.1: (@isaacs)
e091b767ccall-limit@1.1.1 (@isaacs)
e25e2b292glob@7.1.4 (@isaacs)
c40ca2d76inherits@2.0.4 (@isaacs)
f00a74293libnpmsearch@2.0.1 (@isaacs)
8757f67d3marked@0.6.3 (@isaacs)
633befeddmarked-man@0.6.0 (@isaacs)
b2e98a343npm-lifecycle@2.1.1 (@isaacs)
e69537dcenode-gyp@4.0.0 (@isaacs)
23e8b9410query-string@6.8.1 (@isaacs)
572eaffcbtar-stream@2.1.0 (@isaacs)
609f62f31worker-farm@1.7.0 (@isaacs)
3e9891181readable-stream@3.4.0 (@isaacs)

isaacs · 2019-07-02T22:24:32Z

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.

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.

@larsgw

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: #206Close: #206 Reviewed-by: @isaacs

@raywu0123

Credit: @raywu0123 PR-URL: #179Close: #179 Reviewed-by: @isaacs

isaacs requested a review from a team as a code owner July 2, 2019 22:21

isaacs added the release label Jul 2, 2019

isaacsand others added 19 commits July 3, 2019 10:08

lru-cache@5.1.1
429226a

npm-registry-fetch@3.9.1
175670e
This also updates make-fetch-happen, so it no longer requires the old lru-cache.

call-limit@1.1.1
0d0517f

glob@7.1.4
7414004

inherits@2.0.4
bddd60e

libnpmsearch@2.0.1
4acf03f

marked@0.6.3
c2bd172

marked-man@0.6.0
7f0221b

npm-lifecycle@2.1.1
f458fe7

node-gyp@4.0.0
0097529

query-string@6.8.1
0fa2bb4

tar-stream@2.1.0
b864509

worker-farm@1.7.0
25db00f

readable-stream@3.4.0
8dfbe86

fix-xmas-underline
172f9ac
Credit: @raywu0123 PR-URL: #179Close: #179 Reviewed-by: @isaacs

mailmap: Fix 'isaacs' for the gen-changelog script
027742e

doc: changelog for 6.10.1
3013a2d

isaacs force-pushed the release-next-6.10.1 branch from 565a0df to 3013a2dCompare July 3, 2019 17:11

isaacs merged commit 3013a2d into release-nextJul 3, 2019

isaacs deleted the release-next-6.10.1 branch August 19, 2021 16:23

varmakarthik12 mentioned this pull request Oct 13, 2023
[Snyk] Upgrade graceful-fs from 4.2.6 to 4.2.11 varmakarthik12/cli#5
Closed

gutwrinch mentioned this pull request Oct 19, 2023
[Snyk] Upgrade ini from 3.0.1 to 4.1.1 gutwrinch/cli-1#4
Merged

snyk-ioBot mentioned this pull request Oct 22, 2024
[Snyk] Fix for 55 vulnerabilities Graybar-codespace/cli-3#116
Open

Jah-yee pushed a commit to Jah-yee/cli that referenced this pull request Apr 16, 2026
chore: release versions (npm#207)
aaa5c44

github-actionsBot added a commit to Kevinlee7250/cli that referenced this pull request Jul 8, 2026
🤖 봇 응답 (npm#207)
414b335

github-actionsBot added a commit to Kevinlee7250/cli that referenced this pull request Jul 21, 2026
📊 blog1 게시 완료 (npm#207)
b9462df

github-actionsBot added a commit to Kevinlee7250/cli that referenced this pull request Jul 21, 2026
📊 blog2 게시 완료 (npm#207)
45de20b

github-actionsBot added a commit to Kevinlee7250/cli that referenced this pull request Jul 21, 2026
📊 blog3 게시 완료 (npm#207)
9b27cf4

github-actionsBot added a commit to Kevinlee7250/cli that referenced this pull request Aug 18, 2026
🔧 자동 수리 완료 (npm#207)
aeb995e

github-actionsBot added a commit to Kevinlee7250/cli that referenced this pull request Aug 19, 2026
🔥 트렌드 선점 후보 갱신 (npm#207)
cf32d95