Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Did sbt-typelevel-0.4.20 eat us? #184

Closed
rossabaker opened this issue Apr 25, 2023 · 2 comments
Closed

Did sbt-typelevel-0.4.20 eat us? #184

rossabaker opened this issue Apr 25, 2023 · 2 comments

Comments

@rossabaker
Copy link
Member

#182, #183 both failing on a MiMa issue, and MiMa was upgraded in that release. I am slightly afraid I'm at fault via lightbend-labs/mima#743.
@rossabaker
Copy link
Member Author

From #183:

[error] (core-commonJVM / mimaReportBinaryIssues) Failed binary compatibility check against org.typelevel:otel4s-core-common_2.13:0.2.1 (e:info.apiURL=https://***/service/local/repositories/snapshots/archive/org/typelevel/otel4s-docs_2.13/0.2.1-2-31aa229-SNAPSHOT/otel4s-docs_2.13-0.2.1-2-31aa229-SNAPSHOT-javadoc.jar/!/index.html, e:info.versionScheme=early-semver)! Found 1 potential problems
[error] (testkitJVM / mimaReportBinaryIssues) not a directory or jar file: /home/runner/work/otel4s/otel4s/testkit/all/jvm/target/scala-2.13/classes

@rossabaker
Copy link
Member Author

It did not eat us. Just needed to do the close and open do-si-do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rossabaker