Repository navigation
Add sbt-release workflow - #172
Merged
Merged
Conversation
Release an SBT project to Maven Central (Sonatype Central Portal) with sbt-release and sbt-pgp, like gradle-release.yml for Gradle: commit and tag the release version, publish the signed artifacts with sonaRelease, commit the next snapshot version, push, and create the GitHub release. A second release of the same ref is queued instead of cancelling a run midway, which could leave a version published without its tag and version commits.
thescouser89
approved these changes
Nov 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Release an SBT project to Maven Central (Sonatype Central Portal) with sbt-release and sbt-pgp, like gradle-release.yml for Gradle: commit and tag the release version, publish the signed artifacts with sonaRelease, commit the next snapshot version, push, and create the GitHub release.
A second release of the same ref is queued instead of cancelling a run midway, which could leave a version published without its tag and version commits.