Shrinkwrapped modules being skipped?

[w33ble]

There seems to be a version discrepancy with the shipped version and the shrinkwrap file in v4.1.1, in particular with Bluebird.

The shrinkwrap file in v4.1.1 specifies Bluebird version v2.9.27, but the version that shipped with the binary we distribute is using v2.9.30.

Either there's an issue with our build process, or 4.1.1 was built without the shrinkwrap file, in which case there's an issue with our workflow and we need more automation.

[spalger]

Yes, we need better process around this. I think that we need to create a grunt task for doing the release commit, and it should probably go something like this:

rm -rf node_modules
npm install
npm shrinkwrap
git add npm-shrinkwrap.json
git commit -m "version $V"
git tag "v$V"
grunt release
git rm npm-shrinkwrap.json
git commit -m "bump to $NextV"