Razvan

We shoud get not-breaking changes in `v3` as well. Not doing so means discontinuing `v3`, thus leaving all of us, the users, with "latest" legacy. I can help out if...

@mjsalinger Considering the small impact of the (503 -> 500) breaking change, it wouldn't be a problem to go straight to `v4`. However, now that dropping support for `node@4` has...

That's great. Thanks!

My fix is strictly targeted towards `angular 1.4`, since under `angular 1.3` there was nothing to fix. I did this thinking that you are following angular's versioning and not care...

Seems that dev-null [is an extension of the Writeable stream](https://github.com/thlorenz/dev-null/blob/master/index.js#L11) so you should be able to [configure it](https://nodejs.org/dist/latest-v12.x/docs/api/stream.html#stream_implementing_a_writable_stream): `devnull({ objectMode: true })`.

Well, there is a branch for Jasmine 2.0 as minijasminenode2 and it is used in some other modules. I saw that with #17 a silent option has been added to...

@iRevive Has this been accidentally closed?

For transparency, I've found a "hack" to reach the desired behaviour by recovering from the `ResolveException` with an empty `mimaPreviousClassfiles`: ``` mimaPreviousClassfiles := { Try(artifactsToClassfiles.value.toClassfiles(mimaPreviousArtifacts.value)) .recover { case e: sbt.librarymanagement.ResolveException...