Update docs for -release to make it clear it accepts recent Java versions

[rtyley]

The old displayed values of 6, 7, 8, 9 are confusing for developers contemplating updating to recent Java versions like 21 - eg :

I was getting an error that -release:21 is not a valid compiler option when I ran the code. Looking at the docs: https://docs.scala-lang.org/overviews/compiler-options/ my understanding is that this is not supported for Java 21.

That's an incorrect understanding from the docs, as newer Java versions definitely are supported by the -release Scala compiler parameter - so it's best to clarify that!

In this case, the developer was getting the error because they were accidentally running with an older Java version (the compiler error could probably be clearer there too).

[som-snytt]

This is OK but likely to be overwritten if someone runs the automation.

[rtyley]

This is OK but likely to be overwritten if someone runs the automation.

Ah, thank you! I didn't realise this file was auto-generated by automation - searching for the filename, I now see a comment that mentions the generateDocsData command:

over in the scala/scala repo, running sbt followed by generateDocsData generates a compiler-options.yml file, and then the web page is generated from that

I guess generateDocsData isn't run as part of the release process for Scala releases - I tried running it, and got quite a big diff on compiler-options.yml.

[som-snytt]

@rtyley yes, it has limitations; I ought to have written "automation" with more sarcasm; but thanks, accurate doc for compiler options is what everyone asks for.

[rtyley]

accurate doc for compiler options is what everyone asks for.

maybe getting generateDocsData to run as part of the release process could be a ScalaCenter Google Summer Of Code project 😄