greenkeeper[bot]
commented
7 years ago Version 4.2.0 just got published.
Your tests are still failing with this version. Compare the changes 🚨
Release Notes
v4.2.0Hi all! I'm Kat, and I'm currently sitting in a train traveling at ~300km/h through Spain. So clearly, this release should have something to do with speed. And it does! Heck, with this release, you could say we're really blazing, even.
IMPROVED CLI SEARCH~
You might recall if you've been keeping up that one of the reasons for a semver-major bump to npm@4 was an improved CLI search (read: no longer blowing up Node). The work done for that new search system, while still relying on a full metadata download and local search, was also meant to act as groundwork for then-ongoing work on a brand-new, smarter search system for npm. Shortly after npm@4 came out, the bulk of the server-side work was done, and with this release, the npm CLI has integrated use of the new endpoint for high-quality, fast-turnaround searches.
No, seriously, it's fast. And relevant:
Give it a shot! And remember to check out the new website version of the search, too, which uses the same backend as the CLI now.
Incidentally, the backend is a public service, so you can write your own search tools, be they web-based, CLI, or GUI-based. You can read up on the full documentation for the search endpoint, and let us know about the cool things you come up with!
-
ce3ca51#15481 Add an internalgunzip-maybeutility for optional gunzipping. (@zkat) -
e322932a53055ea1f4365c56618c#15481 Add support for using the new npm search endpoint for fast, quality search results. Includes a fallback to "classic" search. (@zkat)
WHERE DID THE DEBUG LOGS GO
This is another pretty significant change: Usually, when the npm process crashed, you would get an npm-debug.log in your current working directory. This debug log would get cleared out as soon as you ran npm again. This was a bit annoying because 1) you would get a random file in your git status that you might accidentally commit, and 2) if you hit a hard-to-reproduce bug and instinctually tried again, you would no longer have access to the repro npm-debug.log.
So now, any time a crash happens, we'll save your debug logs to your cache folder, under _logs (~/.npm on *nix, by default -- use npm config get cache to see what your current value is). The cache will now hold a (configurable) number of npm-debug.log files, which you can access in the future. Hopefully this will help clean stuff up and reduce frustration from missed repros! In the future, this will also be used by npm report to make it super easy to put up issues about crashes you run into with npm.
-
04fca22#11439 Put debug logs in$(npm get cache)/_logsand store multiple log files. (@KenanY) (@othiym23) (@isaacs) (@iarna)
DOCS
-
ae8e71c#15402 Add missing backtick in one of thenpm doctormessages. (@watilde, @charlotteis) -
821fee6#15480 Clarify that unscoped packages can depend on scoped packages and vice-versa. (@chocolateboy) -
2ee45a8#15515 Update minimum supported Node version number in the README tonode@>=4. (@watilde) -
af06aa9#15520 Add section tonpm-scopedocs to explain that scope owners will own scoped packages with that scope. That is, user@aliceis not allowed to publish to@bob/my-packageunless explicitly made an owner by user (or org)@bob. (@hzoo) -
bc892e6#15539 Replacehttpwithhttpsand fix typos in some docs. (@watilde) -
1dfe875#15545 Update Node.js download link to point to the right place. (@watilde)
DEPENDENCIES
MISC
Commits
The new version differs by 20 commits .
59337204.2.0819b6a6update AUTHORSc64def9doc: update changelog for npm@4.2.081ea3e8mississippi@1.3.0b824bfbansi-regex@2.1.11dfe875doc: update Node.js download link (#15545)bc892e6doc: Fix typo and replace http with https (#15539)af06aa9doc: add section about scopes only belonging to user/org (#15520)2ee45a8docs: update supported version number of Node.js (#15515)821fee6doc: clarify that unscoped packages can depend on scoped packages (#15480)d75fc03run-script: keep exit code (#15413)ae8e71cdoctor: close the message brackets (#15402)c56618cdoc: documented new searchlimit optiona1f4365test: tests for new search codea53055econfig: added config for searchlimit
There are 20 commits in total. See the full diff.
Version 4.1.2 of npm just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As npm is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them. I recommend you give this issue a very high priority. I’m sure you can resolve this :muscle:
Status Details
- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/shellscape/npm-version-tree/builds/195520565)Release Notes
v4.1.2v4.1.2 (2017-01-12)
We have a twee little release this week as we come back from the holidays.
0.12 IS UNSUPPORTED NOW (really)
After jumping the gun a little, we can now officially remove 0.12 from our supported versions list. The Node.js project has now officially ended even maintenance support for 0.12 and thus, so will we. To reiterate from the last time we did this:
What this means:
What this doesn't mean:
We're not super interested in taking sides on what version of Node.js you "should" be running. We're a workflow tool, and we understand that you all have a diverse set of operational environments you need to be able to support. At the same time, we are a small team, and we need to put some limits on what we support. Tracking what's supported by our runtime's own team seems most practical, so that's what we're doing.
c7bbba8Remove 0.12 from our supported versions list. (@iarna)WRITING TO SYMLINKED
package.json(AND OTHER FILES)If your
package.json,npm-shrinkwrap.jsonor.npmrcwere a symlink and you used annpmcommand that modified one of these (egnpm config setornpm install --save) then previously we would have removed your symlink and replaced it with an ordinary file. While making these files symlinks is pretty uncommon, this was still surprising behavior. With this fix we now overwrite the destination of the symlink and preserve the symlink itself.a583983write-file-atomic#5 #10223write-file-atomic@1.3.1: When the target is a symlink, write-file-atomic now overwrites the destination of the symlink, instead of replacing the symlink itself. This makes it's behavior matchfs.writeFile.Fixed a bug where it would ALWAYS fs.stat to look up default mode and chown values even if you'd passed them in. (It still used the values you passed in, but did a needless stat.) (@iarna)
DEPENDENCY UPDATES
521f230node-gyp@3.5.0: Improvements to how Python is located. New--devdirflag. (@bnoordhuis) (@mhart)ccd83e8JSONStream@1.3.0: Add new emitPath option. (@nathanwills)TEST IMPROVEMENTS
d76e084Disable metric reporting for test suite even if the user has it enabled. (@iarna)Commits
The new version differs by 0 commits (ahead by 0, behind by 20).
See the full diff.
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: