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

Compile Scala 3 version with Scala LTS (3.3.4) #732

Merged
merged 1 commit into from
Dec 4, 2024

Conversation

Dichotomia
Copy link
Contributor

Compile Scala 3 version with Scala LTS (3.3.4). See issue #731

Compile Scala 3 version with Scala LTS (3.3.4). See issue pac4j#731
@Dichotomia Dichotomia changed the title Compile Scala 3 version with Scala LTS (3.3.4 Compile Scala 3 version with Scala LTS (3.3.4) Dec 4, 2024
@leleuj
Copy link
Member

leleuj commented Dec 4, 2024

Copy that. Thanks

@leleuj leleuj merged commit 830fe2b into pac4j:master Dec 4, 2024
3 checks passed
@Dichotomia
Copy link
Contributor Author

Thanks you for merging this.
Do you think that would be possible to publish a release?
The last patch is unusable within a Scala 3 application for this reason.

@Dichotomia
Copy link
Contributor Author

[error] error while loading scala,
[error] TASTy file scala/NamedTupleDecomposition.tasty could not be read, failing with:
[error] Forward incompatible TASTy file has version 28.6, produced by Scala 3.6.1-bin-nonbootstrapped,
[error] expected stable TASTy from 28.0 to 28.5.
[error] To read this TASTy file, use a newer version of this tool compatible with TASTy 28.6.
[error] Please refer to the documentation for information on TASTy versioning:
[error] https://docs.scala-lang.org/scala3/reference/language-versions/binary-compatibility.html

@leleuj
Copy link
Member

leleuj commented Dec 5, 2024

Sure. I just cut the v12.0.2-PLAY3.0 release. It will show up in the Maven central repo within a few hours/minutes.

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

Successfully merging this pull request may close these issues.

2 participants