Draft
Conversation
Collaborator
Author
|
Blocked on typelevel/sbt-typelevel/issues/851 |
Contributor
|
What does putting multiple 3.something versions into |
Collaborator
Author
|
@durban totally valid point about publish, but before that stage it's useful to see the difference in the build process - at least at the moment of change to a newer scalac. That's why it's a draft and likely to be this way, as a testing ground. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Upgrade to 3.8.1 requires JVM 17+, which should be handled separately in a build process.
Also, it seems worth it to introduce a Scala 3 LTS version into the pipeline.