-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is there a way to specify mimaPreviousArtifacts should include all versions in a range? #483
Comments
Perhaps an "inductive" approach is to use mimaPreviousArtifacts := Set("my.org" %% "proj" % "1.0.+") |
Within a compatible series, it should be adequate to check against any single previous release in that series. It isn’t obvious to me whether it’s “better” to use the oldest in the series or the newest, since it’s hard to see how it could matter. |
Newest is better as, otherwise, you risk losing methods added in a.b.1. Doing this makes the build non-reproducible, so I'm not in favour. But you could implement this today by invoking Coursier in your build definition, get the versions available and then use those versions to specify |
Oh right, of course. (I’m too accustomed to Scala stdlib’s tighter constraints.) |
Good point, and it will often mean that old commits no longer pass the MiMa check since they may not be binary compatible with newer versions. I guess one tricky thing about having it find the prior versions is that you need to be sure you can determine that. We set the version as Perhaps the best approach is just updating |
(that's what I see most OSS projects doing) |
Thank you both for your help! |
further discussion at #724 |
For example, I can write something like:
And I tried the following which weirdly worked locally for one project but not another and failed on Travis and CircleCI:
Is the a canonical way to do this or do I just need to include adding additional versions in my release process?
The text was updated successfully, but these errors were encountered: