Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion project/build.properties
Original file line number Diff line number Diff line change
@@ -1 +1 @@
sbt.version=1.12.15
sbt.version=2.0.6

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🩺 Stability & Availability | 🟠 Major | ⚑ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

if rg -n 'githubWorkflowJavaVersions := Seq\(JavaSpec\.temurin\("11"\)\)' ci.sbt; then
  echo "CI still pins JDK 11"
  exit 1
fi

Repository: nafg/slick-migration-api

Length of output: 247


🌐 Web query:

sbt 2.0 minimum Java version JDK 17

πŸ’‘ Result:

Yes, sbt 2.0 requires a minimum of JDK 17 to run [1][2][3]. The requirement was implemented because sbt 2.x uses Scala 3.8.4 for its metabuild, build definitions, and plugins, which necessitates JDK 17 or higher [2][3]. To enforce this, the official sbt runner scripts are designed to detect the Java version before launch and will fail with an error if the detected environment is using a JDK version lower than 17 [4][5]. For optimal compatibility, the official sbt documentation recommends using Eclipse Adoptium Temurin JDK 17 [1].

Citations:


Set the CI JDK to 17 for sbt 2.

sbt.version=2.0.6 raises the project build to sbt 2.x, which requires JDK 17 or higher. ci.sbt:17 still generates GitHub workflows with Temurin 11, so the generated workflow will fail to run sbt. Update githubWorkflowJavaVersions to use JDK 17.

πŸ€– Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@project/build.properties` at line 1, Update the githubWorkflowJavaVersions
setting in ci.sbt so generated GitHub Actions workflows use Temurin JDK 17
instead of JDK 11, ensuring compatibility with sbt.version 2.0.6.

🎯 Functional Correctness | 🟠 Major | πŸ—οΈ Heavy lift

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

artifact_url="https://repo1.maven.org/maven2/org/scoverage/sbt-coveralls_sbt2_3/1.3.15/sbt-coveralls_sbt2_3-1.3.15.pom"

curl -fsS "$artifact_url" >/dev/null

Repository: nafg/slick-migration-api

Length of output: 213


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "Repo files relevant to sbt/coveralls:"
git ls-files | rg '(^|/)(project/(build\.properties|plugins\.sbt)|plugins\.sbt|\.sc)$|coveralls|sbt-coveralls' || true

echo
echo "project/build.properties:"
if [ -f project/build.properties ]; then cat -n project/build.properties; fi

echo
echo "project/plugins.sbt:"
if [ -f project/plugins.sbt ]; then cat -n project/plugins.sbt; fi

echo
echo "Maven artifact dirs for sbt-coveralls:"
python3 - <<'PY'
import urllib.request, re
from urllib.parse import quote
index = "https://repo1.maven.org/maven2/org/scoverage/sbt-coveralls/"
try:
    text = urllib.request.urlopen(index, timeout=20).read().decode("utf-8")
except Exception as e:
    print("INDEX_ERROR", repr(e))
    text = ""
for tag in re.findall(r'href="([^"]+)/?">[^<]+/</a>', text):
    if re.fullmatch(r'v?\d+\.?\d*\.?\d*[-.a-zA-Z0-9_]+', tag.rsplit("/", 1)[-1]):
        print(index + tag.strip("/") + "/")
PY

Repository: nafg/slick-migration-api

Length of output: 817


🌐 Web query:

repo1.maven.org org scoverage sbt-coveralls_2.12_1.0 1.3.15 sbt-coveralls

πŸ’‘ Result:

The artifact sbt-coveralls_2.12_1.0 version 1.3.15 is an sbt plugin used to upload sbt-scoverage reports to Coveralls [1][2]. It is published under the group ID org.scoverage [1][3]. To use this version in your sbt project, you can add it to your project's plugins by including the following line in your project/plugins.sbt file [1]: addSbtPlugin("org.scoverage" % "sbt-coveralls" % "1.3.15") This artifact is hosted on Maven Central and supports Scala 2.12 and sbt 1.0+ environments [1][3][4]. Further documentation and source code can be found in the official GitHub repository for sbt-coveralls [5].

Citations:


🌐 Web query:

Maven Central org.scoverage sbt-coveralls latest version artifacts sbt coveralls 2 0 sbt2

πŸ’‘ Result:

As of August 9, 2026, the latest version of the sbt-coveralls plugin (org.scoverage:sbt-coveralls) is 1.3.15 [1][2]. Regarding your query about sbt 2.0 support: - The current versions of sbt-coveralls (including 1.3.15) are primarily designed for sbt 1.x [3][4]. - There is currently no official release of sbt-coveralls that explicitly targets or provides native support for sbt 2.0. - While the broader sbt-scoverage plugin has seen active development [5], the sbt-coveralls plugin has not released a 2.0 version to align with the sbt 2.x ecosystem [1][2]. To use the plugin in your project, you can add it to your plugins file as follows: addSbtPlugin("org.scoverage" % "sbt-coveralls" % "1.3.15") [1]

Citations:


Update or remove the sbt 1-only Coveralls plugin.

With project/build.properties set to sbt 2.0.6, addSbtPlugin("org.scoverage" % "sbt-coveralls" % "1.3.15") no longer resolves because sbt-coveralls 1.3.15 is published only for sbt 1.x. Update project/plugins.sbt to an sbt 2-compatible Coveralls plugin, or remove the plugin and any Coveralls usages.

πŸ€– Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@project/build.properties` at line 1, Update the Coveralls configuration in
project/plugins.sbt to use a plugin version compatible with sbt 2.0.6, or remove
the sbt-coveralls declaration and all related Coveralls usages if no compatible
replacement is available. Ensure no references to the sbt 1-only version 1.3.15
remain.

Loading