README: document sbt 1.x vs sbt 2.x version split#622
Conversation
Add a version-matrix table and updated plugins.sbt snippet so users on sbt 1.x know to pin to `0.23.x` (sbt-1 maintenance branch) and users on sbt 2.x pick up `1.x.y` (main). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the README.md to document the compatibility of sbt-pack with sbt 2.x (Scala 3) and sbt 1.x (Scala 2.12), including a version mapping table. Feedback points out that using wildcard versions like "1.x.y" and "0.23.x" in the sbt plugin configuration snippet will cause dependency resolution errors, and suggests replacing them with concrete, copy-pasteable versions.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| // For sbt 2.x (Scala 3) | ||
| addSbtPlugin("org.xerial.sbt" % "sbt-pack" % "1.x.y") | ||
|
|
||
| // For sbt 1.x (Scala 2.12) | ||
| addSbtPlugin("org.xerial.sbt" % "sbt-pack" % "0.23.x") |
There was a problem hiding this comment.
Using literal "1.x.y" and "0.23.x" in the addSbtPlugin configuration will cause dependency resolution errors in sbt, as Ivy/sbt does not support .x wildcards in version strings. It is better to use concrete versions (like "1.0.0" and "0.23.0") so that the snippet is directly copy-pasteable and valid.
| // For sbt 2.x (Scala 3) | |
| addSbtPlugin("org.xerial.sbt" % "sbt-pack" % "1.x.y") | |
| // For sbt 1.x (Scala 2.12) | |
| addSbtPlugin("org.xerial.sbt" % "sbt-pack" % "0.23.x") | |
| // For sbt 2.x (Scala 3) | |
| addSbtPlugin("org.xerial.sbt" % "sbt-pack" % "1.0.0") | |
| // For sbt 1.x (Scala 2.12) | |
| addSbtPlugin("org.xerial.sbt" % "sbt-pack" % "0.23.0") |
1 participant
Summary
// for sbt-0.13.x, sbt-1.xplugins.sbt snippet with two distinct snippets:1.x.yfor sbt 2,0.23.xfor sbt 1.sbt-1maintenance branch.About the 1.0.0 release
This PR only updates docs. The major bump itself is a release-tag action:
```
git tag v1.0.0
git push --tags
```
That triggers the existing release workflow (it runs on
v*tags) and publishes1.0.0to Maven Central. Since the project uses sbt-dynver, no version field inbuild.sbtneeds to change — the tag is the source of truth.Test plan
🤖 Generated with Claude Code