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

Fix release so that it does not attempt to use Scala 2.12 #320

Merged
merged 1 commit into from
Aug 2, 2024
Merged

Fix release so that it does not attempt to use Scala 2.12 #320

merged 1 commit into from
Aug 2, 2024

Commits on Aug 2, 2024

  1. Fix release so that it does not attempt to use 2.12 

    After #318 dropped
support for Scala 2.12, release 8.0.1 correctly no longer published Scala 2.12
artifacts, but unfortunately the 'root' project (which does not have any
code!) was still defaulting to using Scala 2.12, because that is the
default sbt uses if no `scalaVersion` is set.

The next time we tried to do a release (#319 (comment))
the automated-compatibility checking failed, because it saw that one project
was using Scala 2.12, and so it attempted to download all the non-existent
Scala 2.12 artifacts for release 8.0.1 - and failed.

To fix this, we can simply ensure that all modules in this sbt build default
to Scala 2.13, not 2.12 - ie particularly, the 'root' module!
    @rtyley
    rtyley committed Aug 2, 2024
    Configuration menu
    Copy the full SHA
    6574ed3 View commit details
    Browse the repository at this point in the history