The GitHub Actions job "Unit Tests" on pekko-management.git/update/scala-library-3.9.0 has failed. Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run: 42077872bff0889b479c331f2a351277de570add / PJ Fanning <[email protected]> Skip MiMa checks when building with Scala 3.9.0 Motivation: This PR adds Scala 3.9.0 to crossScalaVersions. Scala 3.9.0 shares the "_3" binary suffix with the existing 3.3 artifacts, so `+mimaReportBinaryIssues` picks up the released 3.3-built artifacts and checks them against classes compiled by a much newer compiler. There is no released artifact built with 3.9.0 to compare against, so that check carries no useful signal. Modification: Make the shared `mimaPreviousArtifactsSet` setting resolve to `Set.empty` when `scalaVersion` is `Dependencies.scala3NextVersion`, which covers every module that uses it. Result: `sbt +mimaReportBinaryIssues` still checks Scala 2.13 and Scala 3.3, and reports "mimaPreviousArtifacts is empty, not analyzing binary compatibility" for Scala 3.9.0. Tests: - `sbt -batch "show discovery-kubernetes-api/mimaPreviousArtifacts" "++3.3.8 discovery-kubernetes-api/mimaPreviousArtifacts" "++3.9.0 discovery-kubernetes-api/mimaPreviousArtifacts"` - 2.13 and 3.3.8 keep pekko-discovery-kubernetes-api:1.0.0, 3.9.0 is empty - `sbt -batch scalafmtSbtCheck "++3.9.0 discovery-kubernetes-api/mimaReportBinaryIssues"` - success, the analysis is skipped References: Refs #962 Report URL: https://github.com/apache/pekko-management/actions/runs/33904736403 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
