You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
I think adding explicit API for this has two downsides:
it encourages users to use non-stable versions, which is the opposite of having a reproducible build
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.
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)
Activity
lefou commentedon Jan 20, 2026
I think adding explicit API for this has two downsides:
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.
Gedochao commentedon Jan 20, 2026
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.
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)