Upgrade which to version 2.0.1

[depfu]

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ which (1.3.1 → 2.0.1) · Repo · Changelog

Release Notes

2.0.1 (from changelog)

• generate changelog and publish on version bump
• enforce 100% test coverage
• Promise interface

2.0.0 (from changelog)

• Parallel tests, modern JavaScript, and drop support for node < 8

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 8 commits:

• 2.0.1
• generate changelog and publish on version bump
• enforce 100% test coverage
• Promise interface
• update changelog - 2.0.0
• 2.0.0
• Parallel tests, modern JavaScript, and drop support for node < 8
• update changelog - 1.3.1

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[coveralls]

Coverage remained the same at 80.952% when pulling bd4bd65 on depfu/update/npm/which-2.0.1 into 5cc6602 on master.

[coveralls]

Coverage remained the same at 80.952% when pulling bd4bd65 on depfu/update/npm/which-2.0.1 into 5cc6602 on master.

[coveralls]

Coverage remained the same at 80.952% when pulling bd4bd65 on depfu/update/npm/which-2.0.1 into 5cc6602 on master.