The GitHub Actions job "Update Dependency Graph" on pekko-persistence-r2dbc.git/main has failed. Run started by GitHub user pjfanning (triggered by pjfanning).
Head commit for run: 9b1a7d99c52017c8b353a6195dda09c68968ff90 / Scala Steward <[email protected]> Update scala-library to 3.9.0 (#485) * Update scala-library to 3.9.0 * Update Scala versions in Dependencies.scala * Skip MiMa checks when building with Scala 3.9.0 Motivation: This branch 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: Clear `core / mimaPreviousArtifacts` when `scalaVersion` is `Scala3Next`. The migration module already skips MiMa for all Scala 3 versions, so it needed no change. 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 core/mimaPreviousArtifacts" "++3.3.8 core/mimaPreviousArtifacts" "++3.9.0 core/mimaPreviousArtifacts"` - 2.13 and 3.3.8 keep pekko-persistence-r2dbc:1.0.0, 3.9.0 is empty - `sbt -batch scalafmtSbtCheck "++3.9.0 core/mimaReportBinaryIssues" "++3.9.0 migration/mimaReportBinaryIssues"` - success, both modules skip the analysis References: None - follow-up to the Scala 3.9.0 version bump on this branch * Update build-test.yml --------- Co-authored-by: PJ Fanning <[email protected]> Report URL: https://github.com/apache/pekko-persistence-r2dbc/actions/runs/33913467353 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
