An sbt plugin sbt-ci-release can be used for (semi)automatic deployment of sbt libraries/plugins from GitHub Actions to Nexus Sonatype and Maven Central. It works nicely and it's not even that complicated. We've decided to use it here in this project.
Background
An sbt plugin
sbt-ci-release
can be used for (semi)automatic deployment of sbt libraries/plugins from GitHub Actions to Nexus Sonatype and Maven Central. It works nicely and it's not even that complicated. We've decided to use it here in this project.Feature
At the moment we don't want the release to be fully automatic yet. We've agreed on setting up a GitHub Action for the deployment in a way that the workflow will be manually triggered: https://docs.github.com/en/actions/managing-workflow-runs/manually-running-a-workflow
If we like it, then we might change this to fully automatic deployment (1 commit to master = 1 automatic deployment).
Example
See a similar Issue in our other repository
sbt-git-hooks
: https://github.com/AbsaOSS/sbt-git-hooks/issues/6Proposed Solution
The Readme of https://github.com/sbt/sbt-ci-release describes what to do.