This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of npm.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Hey you all, we've got a couple of bug fixes for you, a slew of documentation improvements and some improvements to our CI environment. I know we just got v4 out the door, but the CLI team is already busy planning v5. We'll have more for you in early December.
BUG FIXES
45d40d9ba2adc21dc89082ba19ee#14403 Fix a bug where a scoped module could produce crashes when incorrectly computing the paths related to their location. This patch reorganizes how path information is passed in to eliminate the possibility of this sort of bug. (@iarna) (@NatalieWolfe)
1011ec6npm/npmlog#46npmlog@4.0.1: Fix a bug where the progress bar would still display even if you passed in --no-progress. (@iarna)
50e51b0#14559 Remove documentation that incorrectly stated that we check .npmrc permissions. (@iarna)
OH UH, HELLO AGAIN NODE.JS 0.12
6f0c353f78bde6#14591 Reintroduce Node.js 0.12 to our support matrix. We jumped the gun when removing it. We won't drop support for it till the Node.js project does so at the end of December 2016. (@othiym23)
Hello lovely humans,
npm just published its new version 4.0.3.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of npm. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
GitHub Release
v4.0.3 (2016-11-17)
Hey you all, we've got a couple of bug fixes for you, a slew of documentation improvements and some improvements to our CI environment. I know we just got v4 out the door, but the CLI team is already busy planning v5. We'll have more for you in early December.
BUG FIXES
45d40d9ba2adc21dc89082ba19ee#14403 Fix a bug where a scoped module could produce crashes when incorrectly computing the paths related to their location. This patch reorganizes how path information is passed in to eliminate the possibility of this sort of bug. (@iarna) (@NatalieWolfe)1011ec6npm/npmlog#46npmlog@4.0.1: Fix a bug where the progress bar would still display even if you passed in--no-progress. (@iarna)DOCUMENTATION UPDATES
c3ac177#14406 Sync up the dispute policy included with the CLI with the current official text. (@mike-engel)9c663b2#14627 Update build status branch in README. (@cameronroe)8a8a0a3#14609 Update examples URLs of GitHub repos where those repos have moved to new URLs. (@dougwilson)7a6425b#14472 Documentsign-git-tagin npm-version(1)'s configuration section. (@strugee)f3087cc#14546 Add a note about the dangers of configuring npm via uppercase env vars. (@tuhoojabotti)50e51b0#14559 Remove documentation that incorrectly stated that we check.npmrcpermissions. (@iarna)OH UH, HELLO AGAIN NODE.JS 0.12
6f0c353f78bde6#14591 Reintroduce Node.js 0.12 to our support matrix. We jumped the gun when removing it. We won't drop support for it till the Node.js project does so at the end of December 2016. (@othiym23)TEST/CI UPDATES
aa73d1cc914e8058fe064#14602 When running tests with coverage, use nyc's cache. This provides an 8x speedup! (@bcoe)ba091ce#14435 Remove an unused zero bytepackage.jsonfound in the test fixtures. (@baderbuddy)DEPENDENCY UPDATES
442e01ereadable-stream@2.2.2: Bring in latest changes from Node.js 7.x. (@calvinmetcalf)bfc4a1cwhich@1.2.12: Remove unused require. (@isaacs)DEV DEPENDENCY UPDATES
7075b05marked-man@0.1.6(@kapouer)3e13featap@8.0.0(@isaacs)The new version differs by 427 commits .
a2a9ba74.0.3b9f4129update AUTHORSb4e871edoc: update changelog for 4.0.3b01f1f4doc: Bring in changelog for 3.10.101011ec6code>npmlog@4.0.1</code442e01ecode>readable-stream@2.2.2</codebfc4a1ccode>which@1.2.12</code3e13feacode>tap@8.0.0</code7075b05code>marked-man@0.1.6</code7e0016dtravis: Now that we aren't avoiding slow tests, stop segregating them58fe064travis: Save the nyc cache between runs2ba19eetest: Add test ensuring bundled deps of scoped packages work1dc8908action: Cleanup the arguments passed to actionsba2adc2finalize: Use gentlyRm instead of bespoke nonsense45d40d9install: Pass in better context to rollbacksThere are 250 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade