Skip to content

Add API for using the latest Scala 3 RC #6630

Open

Description

@Gedochao

Is your feature request related to a problem? Please describe.
I would like to be able to use a set Mill API to make my project's Mill build use the latest Scala 3 Release Candidate version.
This would allow to set up CI jobs automatically testing the project on the latest version without the need to manually check for it and bump it.

The motivation for this is to make it easier and more accessible for projects to test Scala Release Candidate versions and detect issues earlier.

Describe the solution you'd like
Something like:

object foo extends ScalaModule {
  override def scalaVersion = ScalaModule.latestScalaRc
}

Describe alternatives you've considered
Keep setting and bumping this manually.

Additional context
Scala CLI added an equivalent in v1.12.0 at VirtusLab/scala-cli#4016

//> using scala 3.rc

Activity

  1. lefou commented on Jan 20, 2026

    @lefou
    Member

    I think adding explicit API for this has two downsides:

    1. it encourages users to use non-stable versions, which is the opposite of having a reproducible build
    2. it ties some generic logic to some specific use case

    Instead, in #6619 I proposed some generic coursier tooling to query for latest versions of some specific artifact. If applied to the Scala library, user could use it to feed it to the scala version, if they really want to depend on some dynamic version. IMHO, it's better applied to Scala cross-modules, as an additional cross-value.

  2. Gedochao commented on Jan 20, 2026

    @Gedochao
    ContributorAuthor

    it encourages users to use non-stable versions

    To be perfectly honest, we'd like more people to be exposed to the release candidate versions. Even though the release candidate process is lengthy, some regressions go through the cracks.

    IMHO, it's better applied to Scala cross-modules, as an additional cross-value.

    That much is true. Ideally, people would use this as a cross value in their projects for testing.
    It generally doesn't make sense to use the latest RC descriptor otherwise (sometimes there may even be a stable version that's newer)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions