Error in CI when running dependencies feature

[juwara0]

BUG REPORT

• I have ensured that the issue isn't already reported
• I have confirmed that the issue is reproducible with the latest released version
• I have deleted the FEATURE REQUEST / CODE CHANGE section

Summary

• Provide a general summary of the issue in the title above

During the merge build of this repo I received an error that npm prune failed.

https://travis-ci.org/ciena-blueplanet/pr-bumper/builds/397363016#L1738

I tracked this down to possibly being from here:

pr-bumper/lib/bumper.js

Line 431 in 42e9640

return exec('npm prune')

I have disabled the dependency feature in this repo for the time being:

https://github.com/ciena-blueplanet/pr-bumper#featuresdependencies

Removed:

"dependencies": {

•  "enabled": true		
  

• },

from .pr-bumper.josn in PR: #152

Expected Behavior

• What should happen? The build should not error

Actual Behavior

• What happens instead of the expected behavior?
• Is something broken, or not behaving as you expected?
• Attach a screenshot or recording as appropriate.

The build errors: https://travis-ci.org/ciena-blueplanet/pr-bumper/builds/397363016#L1738

Possible Solution

• Not obligatory, but suggest a fix/reason for the bug

I tracked this down to possibly being from here:

pr-bumper/lib/bumper.js

Line 431 in 42e9640

return exec('npm prune')

Steps to Reproduce

• How would you describe your issue to someone who doesn’t know you or your project?
• Try to write a sequence of steps that anybody can repeat to see the issue.
• Be specific! If the bug cannot be reproduced, your issue may be closed.
• Provide a link to a live example, include code to reproduce, or direct us to any relevant files as applicable
• This guide has some additional good information: https://stackoverflow.com/help/mcve

---

• Include the contents of your package.json file
• Steps to reproduce:
  1.
  2.
  3.
  4.
  ...

Context

• How has this issue affected you? What are you trying to accomplish?
• Providing context helps us come up with a solution that is most useful in the real world.

Environment

(answer all that are applicable)

• I am using the latest released version (can check with npm ls <package-name>)
• My version of Node is: 8.6.0
• My version of npm is: 5.3.0
• My OS is:
• Include the contents of your package.json file