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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
π― Functional Correctness | π‘ Minor | β‘ Quick win
π§© Analysis chain
π Script executed:
Repository: nafg/slick-migration-api
Length of output: 1177
π Script executed:
Repository: nafg/slick-migration-api
Length of output: 253
π Script executed:
Repository: nafg/slick-migration-api
Length of output: 7375
π Web query:
SBT 2.0 JDK 17 requirement documentationπ‘ Result:
sbt 2.x requires a minimum of JDK 17 to run [1][2][3]. This requirement is strictly enforced; the sbt runner is designed to detect the JDK version before launching and will terminate with an error message if it detects a version lower than JDK 17 [4]. The decision to move to JDK 17 as the baseline is driven by the fact that sbt 2.x uses Scala 3.8.x for build definitions and plugins [2][3], which itself requires JDK 17 or higher [2][3]. Official documentation recommends using Eclipse Adoptium Temurin JDK 17 [1]. While sbt 2.x requires JDK 17 to execute the build process, you can still compile code targeting older JDK versions (such as JDK 8) by using the --release flag in your build configuration [5].
Citations:
Align the build with SBT 2.x before relying on this version bump.
project/build.propertiesnow pins SBT 2.0.4, which requires JDK 17, but the CI builds and publish job still run with Temurin 11. Update.github/workflows/ci.ymlto JDK 17 and review the SBT 2.x migration notes for plugin/build-definition compatibility before merging.π€ Prompt for AI Agents