Start compiling and publishing PureConfig against Scala 3.1 #1352
Conversation
This file contains 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
ruippeixotog
changed the title
This was referenced Jul 25, 2022
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The latest scalatest version (3.2.12) is compiled against Scala 3.1, forcing us and many other projects that depend on Scala 3 to Scala 3.1 as well. Given how widely used scalatest is, I think it's time for us to drop Scala 3.0 as well and simplify our build assumptions (for now). Compared to scalatest, this PureConfig change has a much smaller blast radius (I suspect most PureConfig users are end projects, not libraries), so I think it won't have a lot of consequences.
On this PR I'm dropping Scala 3.0 and combining a lot of existing open PRs that depend on this, such as bumping scalatest, using SBT 1.7.x and a few other build nits.
Supersedes #1348, #1317 and #1220.