sbt/sbt-ci-release

This system is an sbt plugin designed to automate the publishing of Scala artifacts to Maven repositories. It provides cross-building support for Scala 2.12 and 3, and integrates with multiple CI/CD platforms including GitHub Actions, Azure Pipelines, and GitLab CI to handle secure, signed releases.

The plugin now supports GitLab CI, Azure Pipelines, and GitHub Actions in addition to Travis, CircleCI, and Jenkins, automatically detecting the environment via standard environment variables. It introduces configurable publishing commands through the \CI\_RELEASE\ environment variable, allowing users to override the default \publishSigned\ behavior for SNAPSHOT and release versions. The plugin also enforces stricter security by requiring GPG keys for secure environments, supports GPG 2, and automatically configures SCM information for GitHub repositories using HTTPS, SSH, and Git protocols.

plugin · high confidence

The project has shifted its primary continuous integration provider from Travis CI to GitHub Actions, with Azure Pipelines also added as a supported CI environment. The Travis CI configuration file has been removed, and the documentation has been updated to reflect the new setup, including instructions for configuring Sonatype user tokens and GPG keys within GitHub Actions. Additionally, the plugin's Maven coordinates have been updated from com.geirsson to com.github.sbt, and the repository's default branch name has been standardized to main.

(repo-wide) · high confidence

The build configuration has been updated to support cross-compilation for Scala 2.12.21 and Scala 3.8.4, with sbt versions 1.5.8 and 2.0.0 respectively. Key plugin dependencies have been upgraded: sbt-pgp is now at version 2.3.2, sbt-dynver at 5.1.1, and the test framework munit at 1.3.6. The project organization has been changed to com.github.sbt, and the root project is now configured to skip publishing.

(dependencies) · high confidence

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

• First survey — no prior run to compare against. CAI 57.

• Code Health 99
• Architecture 69
• Maturity 44
• Readiness 67
• Security 65

• 300 commits — 290 feature/other, 10 fixes

• (repo) — 142 commits
• (root) — 93 commits
• project/build.properties — 34 commits
• plugin/src — 14 commits
• .github/workflows — 12 commits
• project/plugins.sbt — 5 commits

• fix: Fix anything that mentions the deprecated OSSRH
• fix: Fix broken Maven Central link to sbt-ci-release
• fix: Merge pull request #372 from sbt/wip/fix
• fix: ci: Fix release
• fix: fix CI (new Ubuntu image lacks sbt) (#318)
• fix: fix a couple of things in the readme
• fix: fix plugin publishing and snapshot publishing
• fix: fix: Fixes SNAPSHOT publishing
• fix: fix: Run +publish on SNAPSHOT
• fix: fix: SNAPSHOT publishing, take 3
• change: Add 'Reformat with scalafmt 3.9.7' to .git-blame-ignore-revs
• change: Added link to SgtSwagrid/scala-library-template in README adopters list.
• change: Be more dynver-aware while dropping tag commands
• change: Bump actions/checkout from 3 to 4 (#282)
• change: Bump actions/checkout from 4 to 5
• change: Bump actions/checkout from 5 to 6
• change: Bump actions/checkout from 6 to 7
• change: Bump actions/setup-java from 3 to 4
• change: Bump actions/setup-java from 4 to 5
• change: Bump actions/setup-java from 5 to 6
• …and 280 more

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

sbt/sbt-ci-release 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.