Skip to content

"3-latest.candidate" for Scala 3 release candidates #8595

@eed3si9n

Description

@eed3si9n

Ref #8590 by @Gedochao

Steps

scalaVersion := "3-latest.candidate"

lazy val p1 = project
  .settings(
    libraryDependencies += "org.typelevel" %% "cats-effect" % "3.6.3"
  )

lazy val p2 = project
  .dependsOn(p1)

Expectation

  1. scalaDynVersion task is added to all subprojects, and resolves to the latest Scala 3 release candidate published to the Central Repo. The implementation should call a private function in LibraryManagement module so the network call is made once per all subprojects, and cached for 24h.
  2. compile, test etc works.

Notes

Eventually it would be nice to push the network call to Coursier so users who are behind the proxy repositories can use this too. However, latest.integration doesn't distinguish RCs from nightlies:

$ cs resolve "org.scala-lang:scala3-compiler_3:latest.integration" | head -n 1
org.scala-lang:scala-library:3.8.1-RC1:default
$ cs resolve "org.scala-lang:scala3-compiler_3:latest.integration" -r https://repo.scala-lang.org/artifactory/local-maven-nightlies/ | head -n 1
org.scala-lang:scala-library:3.8.2-RC1-bin-20260121-137f1c8-NIGHTLY:default

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