sbt/sbt-dynver
59.7
Adequate · 6 November 2026
250
lines of production code
Scala
primary language
4
measurements over time
What this system is
This system is a dynamic versioning tool that generates semantic version strings based on Git repository state. It provides a core library for version parsing and generation, alongside an SBT plugin that integrates this logic into the build process. The system supports multiple SBT versions and allows for configurable version string formatting, including custom prefixes and separators.
Behavioural changes
Refactored DynVer into library and SBT plugin components
The DynVer logic has been restructured to separate the core versioning library from the SBT plugin implementation. The core logic is now contained in \dynver/src/main/scala/sbtdynver/DynVer.scala\, which includes the \GitDescribeOutput\ parser and version generation methods, while a new \NoProcessLogger\ utility in \dynver/src/main/scala/dynver/impl/\ handles silent process execution. This change organizes the codebase to support cross-publishing the library independently of the SBT plugin, allowing users to integrate DynVer's versioning capabilities into non-SBT projects or custom build tools.
dynver/src/main · high confidence
Switch CI from Travis CI to GitHub Actions and pin JGit dependency
The project's continuous integration has moved from Travis CI to GitHub Actions, removing the .travis.yml configuration file. Additionally, the JGit dependency is pinned to version 5.x in the .scala-steward.conf file to maintain compatibility with Java 8, as JGit 6.x requires Java 11.
(repo-wide) · high confidence
sbt-dynver plugin restructured for sbt 2.x compatibility
The sbt-dynver plugin has been refactored to support sbt 2.0.0-RC3, splitting the codebase into a library and an sbt plugin module. This change introduces new build settings such as \dynverVTagPrefix\, \dynverTagPrefix\, and \dynverSeparator\ to allow finer control over version string generation, and adds \dynverAssertTagVersion\ to validate that the version derives from git tags. The plugin now uses slash syntax for settings and includes updated scripted tests to verify behavior across various git states (tags, commits, dirty status) and multi-project setups.
sbtdynver · high confidence
Test coverage
Added comprehensive test suite for DynVer versioning logic
Added new Scala test specifications in \dynver/src/test\ that verify the dynamic version generation behavior across various Git states. The tests cover version string formatting, previous version detection, snapshot status determination, Sonatype snapshot compatibility, and version stability checks, ensuring the library correctly handles scenarios such as uncommitted changes, merge commits, and different tag prefixes.
dynver/src/test · high confidence
Dependencies
Upgrade to sbt 2.0.10 and enable binary compatibility checks
The build system has been upgraded from sbt 0.13.12 to sbt 2.0.10, requiring users to update their local sbt installation. Additionally, the project now includes sbt-mima-plugin (v1.2.1) to enforce binary compatibility checks against the previous version (5.0.0-M3), ensuring that public API changes are detected during builds.
project · high confidence
sbt-dynver split into library and plugin with sbt 2 support
The project has been restructured to separate the core versioning logic into a standalone library (\dynverLib\) and the sbt plugin (\sbt-dynver\), enabling the plugin to be cross-built for both sbt 1.x (via Scala 2.12) and sbt 2.x (via Scala 3). This change updates the organization to \com.github.sbt\, upgrades the Scala library dependencies to 2.12.21, 2.13.18, and 3.3.8, and bumps the JGit dependency to 5.13.3. Additionally, comprehensive scripted tests have been added to verify version string generation across various git states (clean, dirty, tagged, untagged) and configurations (custom prefixes, separators, and multi-project builds).
(dependencies) · high confidence
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
How this codebase got here
Score
- CAI 61 → 60 (-1.3)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.
Lenses
- Code Health 76 → 76 (+0.0)
- Architecture 100 → 100 (+0.0)
- Maturity 50 → 47 (-2.7)
- Readiness 69 → 69 (+0.0)
- Security 65 → 65 (+0.0)
Resolved (1)
- Off-boarding risk: anonymized user #1
New (1)
- Off-boarding risk: anonymized user #1
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
sbt/sbt-dynver was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.
About this page
- The score is its most recent published measurement, taken on 6 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 0fd396963c1c0e7b9c7df21575548efb974ff61e — the exact code this score is about.
- Scored under rubric-2026.11.2 — the same rubric and the same method as every other entry in this index.
- Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.3+preprod-60d1b390edf0.