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

deps: upgrade to npm 2.11.2 #1956

Closed
wants to merge 3 commits into from
Closed

deps: upgrade to npm 2.11.2 #1956

wants to merge 3 commits into from

Conversation

iarna
Copy link
Member

@iarna iarna commented Jun 12, 2015

https://github.com/npm/npm/releases/tag/v2.11.2 has the details. Version bumps, doc fixes and some minor bug fixes.

r: @Fishrock123
r: @chrisdickinson

iarna and others added 3 commits June 12, 2015 04:04
Every npm version bump requires a few patches to be floated on
node-gyp for io.js compatibility. These patches are found in
03d1992,
5de334c, and
da730c7. This commit squashes
them into a single commit.

PR-URL: nodejs#990
Reviewed-By: Ben Noordhuis <[email protected]>
The delay-load hook allows node.exe/iojs.exe to be renamed. See efadffe
for more background.

PR-URL: nodejs#1433
Reviewed-By: Ben Noordhuis <[email protected]>
@silverwind silverwind added the npm Issues and PRs related to the npm client dependency or the npm registry. label Jun 12, 2015
@thefourtheye
Copy link
Contributor

We could have landed 2.11.3, right?

@iarna
Copy link
Member Author

iarna commented Jun 12, 2015

@thefourtheye You could but it's not gotten it's week of testing by our bleeding edge testers. 2.11.2 is the current stable release. We started this process due to node.js having to have some emergency releases due to npm brokenness. Personally I would not recommend skipping the process. ¯_(ツ)_/¯

@thefourtheye
Copy link
Contributor

@iarna Cool then 👍

Fishrock123 pushed a commit that referenced this pull request Jun 15, 2015
PR-URL: #1956
Reviewed-By: Jeremiah Senkpiel <[email protected]>
@Fishrock123
Copy link
Contributor

Thanks, landed in 5c2707c...953b3e7 :)

@rvagg rvagg mentioned this pull request Jun 16, 2015
rvagg added a commit that referenced this pull request Jun 23, 2015
PR-URL: #1996

Notable changes

* module: The number of syscalls made during a require() have been
  significantly reduced again (see #1801 from v2.2.0 for previous
  work), which should lead to a performance improvement
  (Pierre Inglebert) #1920.
* npm:
  - Upgrade to v2.11.2 (Rebecca Turner) #1956.
  - Upgrade to v2.11.3 (Forrest L Norvell) #2018.
* zlib: A bug was discovered where the process would abort if the
  final part of a zlib decompression results in a buffer that would
  exceed the maximum length of 0x3fffffff bytes (~1GiB). This was
  likely to only occur during buffered decompression (rather than
  streaming). This is now fixed and will instead result in a thrown
  RangeError (Michaël Zasso) #1811.
rvagg added a commit that referenced this pull request Jun 23, 2015
PR-URL: #1996

Notable changes

* module: The number of syscalls made during a require() have been
  significantly reduced again (see #1801 from v2.2.0 for previous
  work), which should lead to a performance improvement
  (Pierre Inglebert) #1920.
* npm:
  - Upgrade to v2.11.2 (Rebecca Turner) #1956.
  - Upgrade to v2.11.3 (Forrest L Norvell) #2018.
* zlib: A bug was discovered where the process would abort if the
  final part of a zlib decompression results in a buffer that would
  exceed the maximum length of 0x3fffffff bytes (~1GiB). This was
  likely to only occur during buffered decompression (rather than
  streaming). This is now fixed and will instead result in a thrown
  RangeError (Michaël Zasso) #1811.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
npm Issues and PRs related to the npm client dependency or the npm registry.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants