-
Currently, if the return type of a method changes between two library versions, Mima Lib reports an "IncompatibleResultTypeProblem" that has, by default, a "fixable" status. This is too optimistics si…
dotta updated
5 years ago
-
As per REST API reference: https://cloud.google.com/pubsub/docs/reference/rest/v1/PubsubMessage
`messageId` property should not be set when publishing.
I understand it's a breaking change.
I th…
-
I have a change from
```scala
trait DialogSource[+A] { def show(): A }
implicit final class OptionPane(val source: (javax.swing.JOptionPane, String))
extends DialogSource[Any] {
def show…
Sciss updated
5 years ago
-
The check introduced in #263 may be inconvenient when you're cross-building and only have previous artifacts for some of the upstream versions you are targeting.
-
We will have to break binary compatibility to fix #89 and #90
-
We have #921 that apparently breaks binary compat.
Unfortunately we've broken binary compat far too often. We can't afford to piss off our users on every release, especially since we have downstrea…
-
## What happened?
I made some internal code breaks. I resolved the breaks, but this was against an "old" tag i.e. someone released just after I resolved the breaks, so when this merged, I got a sem…
-
List of things that ought to be done before sbt `1.3.0` final
- [ ] add mima to the sbt-coursier repo, to prevent binary breakages for the `lm-coursier-shaded` module (that sbt depends on)
- [ ] a…
-
Due to an [incorrectly configured Mima setup](#1631), we didn't notice that the master branch is no longer binary compatible with the 2.0.0 release. Using #1631 as a starting point, I bisected to dete…
-
since 0.4.0
https://github.com/lightbend/mima/commit/40a2cbe042a203f8fddfb02b0a27907f6c6dc93d
build.sbt
```scala
scalaVersion := "2.12.8"
// works
mimaPreviousArtifacts := Set(
"org.s…