Configure outcome when previous artifact is not found

[razvanz]

I have a setup where the patch release version is automatically incremented during the release process without it being set in the version.sbt file. I assumed that mimaFailOnNoPrevious would account for the situation when the previous artifact is not found, but it does not. This leads to a situation where I need to disable the compatibility check for the first major release and re-enable it right after, which is an annoying and error-prone affair.

Would it be possible to have the compatibility check succeed if a previous artifact is not found? If not, how about adding a new configuration option, mimaFailOnNotFound := true/false?

[razvanz]

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 => Map.empty[ModuleID, File] }
            .get
        }