mima compare version #331
Merged
mima compare version #331
Conversation
This file contains 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
pjfanning
requested review from
He-Pin,
nvollmar,
mdedetrich and
samueleresca
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.
we are getting issues in
mainbranch builds with mima checks - since the v1.1.0-M0 git tag was addedsee https://github.com/apache/incubator-pekko-connectors/actions/runs/7678675966/job/20928810106
the issue is because the current setup uses the git tags and expects there to be releases for every git tag
We can test with "1.0.2" for the time being
I raised sbt/sbt-dynver#283 to possibly do a change there so that we could go back to using the
previousStableVersionsbt variable.