Is there a way to specify mimaPreviousArtifacts should include all versions in a range?
See original GitHub issueFor example, I can write something like:
mimaPreviousArtifacts := {
val versions = "1.0.0" :: "1.0.1" :: "1.0.2" :: Nil
Set(versions.map("my.org" %% "proj" % _): _*)
}
And I tried the following which weirdly worked locally for one project but not another and failed on Travis and CircleCI:
mimaPreviousArtifacts := Set("my.org" %% "proj" % "1.0.*")
Is the a canonical way to do this or do I just need to include adding additional versions in my release process?
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
"mimaPreviousArtifacts not set" check may be too strict #328
The check introduced in #263 may be inconvenient when you're cross-building and only have previous artifacts for some of the upstream versions ......
Read more >Specifying version range - IBM
In the Contained Bundles section, select the bundle for which you want to specify version information. Click Properties. In the OSGi bundle properties...
Read more >Is it possible to install with pip a version range of a package ...
As there is no room for any version range with pip+git, I will use a workaround and write a python script that will...
Read more >Package Management: Stop Using Version Ranges - Lucidchart
They inhibit building and using older versions of the project, complicate bug reports ... There are several ways to overcome version ranges.
Read more >sbt-version-policy - Scaladex
Your next release will provide no compatibility guarantees with the ... This means that you have to set this key to the next...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thank you both for your help!
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
1.0-SNAPSHOT
in the intermediate versions (for example, between1.0.1
and1.0.2
) so unless we are careful to keep all prior releases as ancestor commits, this wouldn’t work either.Perhaps the best approach is just updating
mimaPreviousArtifacts
as part of the release process.