1+ ### v4.1.2 (2017-01-12)
2+
3+ We have a twee little release this week as we come back from the holidays.
4+
5+ #### 0.12 IS UNSUPPORTED NOW (really)
6+
7+ After [ jumping the gun a
8+ little] ( https://github.com/npm/npm/releases/tag/v4.0.2 ) , we can now
9+ officially remove 0.12 from our supported versions list. The Node.js
10+ project has now officially ended even maintenance support for 0.12 and thus,
11+ so will we. To reiterate from the last time we did this:
12+
13+ What this means:
14+
15+ * Your contributions will no longer block on the tests passing on 0.12.
16+ * We will no longer block dependency upgrades on working with 0.12.
17+ * Bugs filed on the npm CLI that are due to incompatibilities with 0.12
18+ (and older versions) will be closed with a strong urging to upgrade to a
19+ supported version of Node.
20+ * On the flip side, we'll continue to (happily!) accept patches that
21+ address regressions seen when running the CLI with Node.js 0.12.
22+
23+ What this doesn't mean:
24+
25+ * The CLI is going to start depending on ES2015+ features. npm continues
26+ to work, in almost all cases, all the way back to Node.js 0.8, and our
27+ long history of backwards compatibility is a source of pride for the
28+ team.
29+ * We aren't concerned about the problems of users who, for whatever
30+ reason, can't update to newer versions of npm. As mentioned above, we're
31+ happy to take community patches intended to address regressions.
32+
33+ We're not super interested in taking sides on what version of Node.js
34+ you "should" be running. We're a workflow tool, and we understand that
35+ you all have a diverse set of operational environments you need to be
36+ able to support. At the same time, we _ are_ a small team, and we need
37+ to put some limits on what we support. Tracking what's supported by our
38+ runtime's own team seems most practical, so that's what we're doing.
39+
40+ * [ ` c7bbba8 ` ] ( https://github.com/npm/npm/commit/c7bbba8744b62448103a1510c65d9751288abb5d )
41+ Remove 0.12 from our supported versions list.
42+ ([ @iarna ] ( https://github.com/iarna ) )
43+
44+ #### WRITING TO SYMLINKED ` package.json ` (AND OTHER FILES)
45+
46+ If your ` package.json ` , ` npm-shrinkwrap.json ` or ` .npmrc ` were a symlink and
47+ you used an ` npm ` command that modified one of these (eg ` npm config set ` or
48+ ` npm install --save ` ) then previously we would have removed your symlink and
49+ replaced it with an ordinary file. While making these files symlinks is pretty
50+ uncommon, this was still surprising behavior. With this fix we now overwrite
51+ the _ destination_ of the symlink and preserve the symlink itself.
52+
53+ * [ ` a583983 ` ] ( https://github.com/npm/npm/commit/a5839833d3de7072be06884b91902c093aff1aed )
54+ [ write-file-atomic/#5 ] ( https://github.com/npm/write-file-atomic/issues/5 )
55+ [ #10223 ] ( https://github.com/npm/npm/10223 )
56+ 57+ When the target is a symlink, write-file-atomic now overwrites the
58+ _ destination_ of the symlink, instead of replacing the symlink itself. This
59+ makes it's behavior match ` fs.writeFile ` .
60+
61+ Fixed a bug where it would ALWAYS fs.stat to look up default mode and chown
62+ values even if you'd passed them in. (It still used the values you passed
63+ in, but did a needless stat.)
64+ ([ @iarna ] ( https://github.com/iarna ) )
65+
66+ #### DEPENDENCY UPDATES
67+
68+ * [ ` 521f230 ` ] ( https://github.com/npm/npm/commit/521f230dd57261e64ac9613b3db62f5312971dca )
69+ 70+ Improvements to how Python is located. New ` --devdir ` flag.
71+ ([ @bnoordhuis ] ( https://github.com/bnoordhuis ) )
72+ ([ @mhart ] ( https://github.com/mhart ) )
73+ * [ ` ccd83e8 ` ] ( https://github.com/npm/npm/commit/ccd83e8a70d35fb0904f8a9adb2ff7ac8a6b2706 )
74+ 75+ Add new emitPath option.
76+ ([ @nathanwills ] ( https://github.com/nathanwills ) )
77+
78+ #### TEST IMPROVEMENTS
79+
80+ * [ ` d76e084 ` ] ( https://github.com/npm/npm/commit/d76e08463fd65705217624b861a1443811692f34 )
81+ Disable metric reporting for test suite even if the user has it enabled.
82+ ([ @iarna ] ( https://github.com/iarna ) )
83+
184### v4.1.1 (2016-12-16)
285
386This fixes a bug in the metrics reporting where, if you had enabled it then
@@ -10,7 +93,7 @@ Anyway, this is a quick release to fix that bug:
1093
1194* [ ` 51c393f ` ] ( https://github.com/npm/npm/commit/51c393feff5f4908c8a9fb02baef505b1f2259be )
1295 [ #15237 ] ( https://github.com/npm/npm/pull/15237 )
13- Don't launch a metrics sender process if we're runnning from a metrics
96+ Don't launch a metrics sender process if we're running from a metrics
1497 sender process.
1598 ([ @iarna ] ( https://github.com/iarna ) )
1699
0 commit comments