Closed vajahath closed 7 years ago
I know, but the only way to fix it would be to publish a new release.
You can release it by a patch update. Let it move from 2.1.0 to 2.1.1 and mention it on change log. This looks necessary, bcz the "build unknown" passes wrong message to audience and leaves bad impression.
At npm clone website the build is failing .
Seems like you used
travis-ci.org/pvorb/node-clone/
instead oftravis-ci.org/pvorb/clone
.