node 6.7.0

[JLHwung]

Created with brew bump-formula-pr.

[dunn]

Does npm need to be bumped?

[DomT4]

Nope. We bumped it too hard quite considerably last time, so upstream are going to be playing catchup for a while, heh.

Merged in bd05ec3. Thank you for another contribution to Homebrew @JLHwung! 😺.

[JLHwung]

@DomT4 What's the policy of bumping npm version of node? Here is the comments from the source

# We track major/minor from upstream Node releases.
# We will accept *important* npm patch releases when necessary.

I would like to make sure if this is the bumping policy.

AFAIK node 6.7.0 does not bundle npm 3.10.7. So, is 3.10.7 an important patch releases or just a situation where it is bumped accidentally?

[DomT4]

We track what Node bundles upstream, unless what Node bundles upstream has security or major usability problems resolved in a newer release. Our last bump was just too heavy on the npm update, but no point reverting, will just try to avoid further npm updates till upstream catches us up.

Sent from my iPhone

On 28 Sep 2016, at 05:32, Junliang Huang [email protected] wrote:

@DomT4 What's the policy of bumping npm version of node? Here is the comments from the source

We track major/minor from upstream Node releases.

We will accept important npm patch releases when necessary.

I would like to make sure if this is the bumping policy.

AFAIK node 6.7.0 does not bundle npm 3.10.7. So, is 3.10.7 an important patch releases or just a situation where it is bumped accidentally?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[JLHwung]

@DomT4 Crystal clear for the policy.

If last bump is just too heavy, how about rolling back to 3.10.3 and align with the upstream? Or do it last time when version is bumped without any npm updates.

[DomT4]

Nobody's reported any problems so let's leave it where it is and just try to remember in future to keep it as in sync as possible.

[mech]

Encounter the strange:

(node:4558) Warning: Possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit

with NPM -v3.10.7, reportedly fixed on -v3.10.8

Just annoying warnings, but NPM appear still working.