-
@non [says](https://contributors.scala-lang.org/t/the-future-of-scalacheck-maintenance/3563/10):
> So talking to @rickynils, it sounds like he plans to move the project to Typelevel, as per the sug…
-
Enable the MiMa checks once the first version of Alpakka InfluxDB is released.
ennru updated
5 years ago
-
MiMa was going to be updated in #508 to version 0.5.0 from 0.3.0, but there are a lot of complaints. They also aren't the same complaints: They differ for Scala version, and for compiler target (JVM…
-
* [x] update master to release with it
* [x] manually release the latest 2.5 version with it
* [ ] update `project/MiMa.scala` to check binary compatibility of 2.13 artifacts against 2.5 as well #27…
-
Please publish zio/interop-reactive-streams against ZIO 1.0.0-RC12-1
According to MIMA, multiple ABI changes happened in ZStream between zio-stream 1.0.0-RC11-1 and 1.0.0-RC12-1, which makes a syst…
-
backwards-only is fine, and I think we could give ourselves permission to be liberal about bumping the version number as needed, in order not to be too saddled by this
-
In some recent PRs I've been fixing up parts of the implementation. In doing so I've changed some class and method definitions and MiMa reports them as binary API breakage. But what is MiMa's public…
-
``` scala
java.lang.NoClassDefFoundError: scala/tools/scalap/scalax/rules/scalasig/ScalaSigSymbol
```
http://stackoverflow.com/questions/30229861/when-i-convert-an-object-to-json-with-json4s-in-a-sbt…
-
I was playing around with `mimaPreviousVersion := None` in scala-parser-combinators and the command `mimaPreviousArtifacts` returns:
```
[info] scala-parser-combinators / mimaPreviousArtifacts
[inf…
-
When Alpakka 1.1.0 is out.
https://github.com/akka/alpakka/blob/be3b89adff40a3ad478d16a43436d5447340cc31/build.sbt#L178