release 0.12.0 about mocha-multi HOT 9 CLOSED

Looking at the changes from the last version all together, the summary seems to be:

Expanded peerDependency range to include mocha 4, which required no changes
Made a bunch of backwards incompatible changes

I'm not clear anything has been gained by doing this from an end-user point-of-view.

Have I missed anything?

from mocha-multi.

@glenjamin it won't print out an ugly peerDep warning.

from mocha-multi.

@glenjamin also fixes:

Support running mocha without a run callback

from mocha-multi.

@glenjamin ping.

from mocha-multi.

I've released 0.11.1 which contains the dependency bumps but none of the breaking changes.

Haven't yet decided where I stand on making the breaking changes.

from mocha-multi.

@glenjamin FYI, semver supports breaking changes on any 0.x release.

from mocha-multi.

but good choice on the 0.11.1 release

from mocha-multi.

My main concern is how many users a release forces to make changes, and whether they get any benefit in exchange for that work.

from mocha-multi.

from mocha-multi.