sbt-version-policy
Compatibility checks for your dependencies (by scalacenter)
tasty-mima
TASTy Migration Manager (by scalacenter)
| sbt-version-policy | tasty-mima | |
|---|---|---|
| 2 | 1 | |
| 80 | 9 | |
| - | - | |
| 7.6 | 6.9 | |
| 9 days ago | 2 months ago | |
| Scala | Scala | |
| Apache License 2.0 | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
sbt-version-policy
Posts with mentions or reviews of sbt-version-policy.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-09-07.
-
Semver violations are common, better tooling is the answer
In the Scala ecosystem, MiMa [1] has been in widespread use for years. It automatically checks compatibility for the binary API of a library. Every library with any amount of success uses it. One could say it's the foundation of a stable ecosystem. We also have sbt-version-policy [2] to set it up with minimal configuration (and directly relate it to SemVer).
More recently, we got tasty-mima [3], which checks compatibility at the type system level, rather than the binary level.
[1] https://github.com/lightbend/mima
[2] https://github.com/scalacenter/sbt-version-policy
[3] https://github.com/scalacenter/tasty-mima
-
SBT Version Scheme Enforcer Plugin: Automatically configure MiMa for Early Semver/PVP/Semver
Can you compare/contrast to https://github.com/scalacenter/sbt-version-policy ?
tasty-mima
Posts with mentions or reviews of tasty-mima.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-09-07.
-
Semver violations are common, better tooling is the answer
In the Scala ecosystem, MiMa [1] has been in widespread use for years. It automatically checks compatibility for the binary API of a library. Every library with any amount of success uses it. One could say it's the foundation of a stable ecosystem. We also have sbt-version-policy [2] to set it up with minimal configuration (and directly relate it to SemVer).
More recently, we got tasty-mima [3], which checks compatibility at the type system level, rather than the binary level.
[1] https://github.com/lightbend/mima
[2] https://github.com/scalacenter/sbt-version-policy
[3] https://github.com/scalacenter/tasty-mima
What are some alternatives?
When comparing sbt-version-policy and tasty-mima you can also consider the following projects:
sbt-version-scheme-enforcer - A SBT Plugin Which Automatically Configures MiMa Based On Your Version Scheme (SemVer, PVP, etc)