Ondra Pelech

> do you have a case in mind where putting it in documentation is clearer? Not really, to be hones. I guess I have this intuition about generating code that...

Oh, in that sense (ScalablyTyped, ScalaPB, Guardrail, ...), I am too :100: But this felt a little bit different to me.

I think we should publish Scala 3 build, at least for Scala Native. doesn't seem to work with Scala Native, because it brings dependencies on libraries ([on Maven Central](https://search.maven.org/artifact/org.portable-scala/portable-scala-reflect_native0.4_2.13/1.1.1/jar)): ```scala...

Hello @sjrd @gzm0 , could we please get review on this PR? :pray: It will unblock the rollout of Scala Native 0.5.x :rocket:

@gzm0 if I understand the PR correctly, we're dropping only support (cross-compilation target) for an old version of Scala (2.11). That shouldn't require a major bump release. The code of...

> If you do not publish it a Scala 2.11 cannot use it anymore. Scala 2 libraries need to be published for the minor Scala version. A library published for...

> why it is even necessary to drop any support here? It seems we could keep expanding our build matrix instead, as we usually do? Of course, that's entirely possible....

> Does the sbt version bump force a downstream bump? Not at all.

Is there any think blocking this PR? If yes, how can I help moving it forward? There's a lot of interest in getting this merged and released, because of lot...

@gzm0 what do you mean? I see only changes in sbt setting to enable Scala Native 0.5.x. What changes do you think should be left out?