Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

use Scala LTS - 3.3.x #355

Closed
visma-alexander-maslov opened this issue Jun 7, 2024 · 1 comment
Closed

use Scala LTS - 3.3.x #355

visma-alexander-maslov opened this issue Jun 7, 2024 · 1 comment

Comments

@visma-alexander-maslov
Copy link

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

@visma-alexander-maslov
Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant