Bluebird warnings not resolved

[dhm116]

It looks like when #58 was resolved by merging #59 and libcipm was published to npm as v3.0.3, it was actually tagged and published as v3.0.3 without the merged fixes from #59.

The latest branch does indeed include the fixes from #59, however you can also see that the package.json file was not updated properly to v3.0.3.

Would it be possible to re-tag latest as v3.0.4 and republish? At least that way this fix could be included whenever the next NPM release is made available.

Thanks!

[jplock]

@jehy @zkat any thoughts on this one?

[jehy]

Yup, I think that it is an important fix, but I grew a bit tired from pushing this pull request for a long time (October 2018)...

Also it seems that there are new accepted PRs so it would be really good to publish a new version.