Replies: 1 comment 2 replies
-
|
Although Mill supports Scala 3.8, I don't think we want switch our code-base to Scala 3.8, since it will drop support for all Java runtimes lower than Java 17. Of course, we encourage the use of the newest JVM/JDK/Scala version, I think we want to keep that Java 11 compatibility a bit longer. I don't see any feature we can't implement because we stay on Scala 3.7.x. We might want to cross-back-publish |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have released Mill
1.1.0-RC1, with an eye to releasing1.1.0final in December. The two big features of Mill1.1.0is support for config-based modules defined inbuild.mill.yamlfiles, and single-file.java,.scala, or.ktscripts with YAML build headers. These are discussed more in the changelog below and linked documentation:The current plan is to synchronize the 1.1.0 release with the Scala 3.8 release also expected by end of the year, such that Mill 1.1.0 will be the first Mill version on Scala 3.8.0. Until then, that gives users 1-2 months to try out the new features and report and issues or bugs, and for us maintainers to polish up the 1.1.0 release.
Please leave any comments, feedback or discussion in this thread
Beta Was this translation helpful? Give feedback.
All reactions