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
It feels like for the generally used library it is better to stick to the LTS branch and and upgrade to the next one when it is absolutely necessary. Maybe even release in parallel 2 different artifacts, not sure.
Now the latest version of scalapb-validate seems to break builds which depend on LTS Scala 3.3.3 as compiler seems to not be able to read TASTY format from the 3.4.2.
New LTS 3.3.4 has been released. https://www.scala-lang.org/download/3.3.4.html
I think this library need to depend on LTS version, not simply the latest scala which ScalaSteward brings
now as Scala has this LTS thing in place https://virtuslab.com/blog/technology/the-scala-3-compatibility-story/#lts-and-scala-next
It feels like for the generally used library it is better to stick to the LTS branch and and upgrade to the next one when it is absolutely necessary. Maybe even release in parallel 2 different artifacts, not sure.
Now the latest version of scalapb-validate seems to break builds which depend on LTS Scala 3.3.3 as compiler seems to not be able to read TASTY format from the 3.4.2.
some info about versioning and binary compatibility
https://virtuslab.com/blog/technology/the-scala-3-compatibility-story/
https://docs.scala-lang.org/scala3/reference/language-versions/binary-compatibility.html
https://www.scala-lang.org/blog/2022/08/17/long-term-compatibility-plans.html
The text was updated successfully, but these errors were encountered: