Notes on upgrades from v0.11.3 dependencies to now

sails_rc5_dependencies.txt

Following is the list of top-level non-development dependencies with their versions in v0.11.x and notes detailing the version they are upgraded to in v0.12.x (if any) and why.  New dependencies (like `consolidate`) have notes explaining the choice of current version.

├── anchor@~0.10.5 (ours)
├── async@0.9.2 -> 0.10.5 (has changelog, lots of bug fixes and good stuff)
├── captains-log@~0.11.11 (ours)
├── colors@0.6.2 -> 1.1.2 (no changelog, but seems to be just bugfixes and it's only used for logs)
├── commander@2.1.0 -> 2.9.0 (has changelog, bugfixes et al)
├── connect@2.25.0 -> 2.29.1 (required by our express version)
├── connect-flash@0.1.1 (latest)
├── consolidate@0.12.1 (latest is just react/promises stuff)
├── cookie@0.1.2  (upgrade causes angst for connect; only used briefly )
├── cookie-signature@1.0.4 -> 1.0.6 (minor fixes)
├── ejs@0.8.8 -> 2.3.4 (we've been using it, guess it works, could use some tests)
├── ejs-locals@1.0.2 (latest)
├── express@3.16.0 -> 3.20.2 (thoroughly tested)
├── express-handlebars@1.0.3 (latest)
├── fs-extra@0.8.1 -> 0.18.4 (been using it, only used on tests, further changelog looked meh)
├── glob@3.2.11 -> 5.0.15 (only used in one spot, been using, but v6 has breaking changes)
├── grunt@0.4.2 -> 0.4.5 (been using)
├── grunt-cli@0.1.13 (latest)
├── grunt-contrib-clean@0.5.0 -> 0.6.0 (been using, but 0.7.0 is mostly dep changes of ~ to ^, tested w/ rigging)
├── grunt-contrib-coffee@0.10.1 -> 0.13.0 (seems fine)
├── grunt-contrib-concat@0.3.0 -> 0.5.1 (tested w/ project, changelog looks good)
├── grunt-contrib-copy@0.5.0 (updating breaks projects w/ many assets)
├── grunt-contrib-cssmin@0.9.0 (updating breaks projects w/ many assets)
├── grunt-contrib-jst@0.6.0 (latest)
├── grunt-contrib-less@0.11.1 -> 1.1.0 (tested w/ project, mostly updates to underlying less which is bugfixes)
├── grunt-contrib-uglify@0.4.1 -> 0.7.0 (further updating breaks projects w/ many assets)
├── grunt-contrib-watch@0.6.1. (tested w/ project)
├── grunt-sails-linker@~0.9.6 (ours)
├── grunt-sync@0.0.8 -> 0.2.4 (tested w/ project)
├── i18n@0.5.0 (latest)
├── include-all@~0.1.6 (ours)
├── lodash@2.4.2 (upgrading breaks projects.  would be worth fixing the issues w/ upgrading to 3.x, but leaving for now)
├── merge-defaults@0.1.4 -> ~0.2.1 (ours)
├── method-override@2.3.5 (latest)
├── mock-req@0.1.0 -> 0.2.0 (commits look good)
├── mock-res@0.1.0 -> 0.3.0 (commits look good)
├── pluralize@0.0.12 -> 1.2.1 (adds more wurds)
├── prompt@0.2.14 (latest)
├── rc@0.5.5 -> 1.0.1 (been using, but no tests--could use some tests)
├── reportback@~0.1.9 (ours)
├── sails-build-dictionary@~0.10.1 (ours)
├── sails-disk@~0.10.8 (ours)
├── sails-generate@~0.12.4 (ours)
├── sails-hook-sockets@~0.12.0 (ours)
├── sails-stringfile@~0.3.2 (ours)
├── sails-util@~0.10.6 (ours)
├── semver@2.2.1 -> 5.1.0 (been using 4.3.6, update is mostly about non-node usage and comments)
├── skipper@0.5.8 (ours)
├── uid-safe@1.1.0 (fine for us, update is for promise stuff)
└── waterline@0.10.28 (ours)

Right- updating lodash or async is a good idea, but would be a breaking change. We could do it for 0.12