Repository navigation
Set up MiMa binary compatibility checks - #79
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
sbt-mima-pluginand a CI job that checks binary compatibility against the previous stable release. The setup follows sage.coreJVM row compares againstpreviousStableVersionfrom sbt-dynver, currently 0.3.0. The JS and Native rows compile the same sources, so they are not checked separately.sbt mimaalias runscore/mimaReportBinaryIssues.mimajob inci.yml. It is not a dependency ofpublish. On a release build, HEAD is the new tag and MiMa compares it with the tag before it, so an intentional breaking release (for example 0.4.0) would otherwise block publishing.Verified locally:
sbt mimapasses against 0.3.0.