Search Gradle plugins

Plugin Latest Version


A plugin which sets a semantic version including a branch qualifier to project.version

(20 July 2017)


The Baseline Gradle plugin lets you verify that the OSGi semantic versioning rules are obeyed by your OSGi bundle.

(17 September 2019)


An easy Gradle plugin that follows rules to automatically generate the Patch version, Build number and Code version, while Major, Minor and Pre-Release suffix remain under our control.

(25 June 2019)


Plugin to set version information in maven POM, java or kotlin files, and git tags

(11 June 2019)


Infer a project's version from your Git repository

(03 June 2019)


Makes available all GitVersion properties to the gradle build (i.e. GitVersion.SemVer). Run task GitVersion for a list of all properties. Requires GitVersion installed

(24 May 2019)


A Gradle plugin that forces semantic versioning and relies on git to detect the project state

(21 May 2019)


Xeno's Semantic Versioning with Git

(22 February 2019)


Gradle Versioning Plugin

(11 September 2018)


This is a Gradle settings-plugin that provides support for semantic versioning of builds. It is quite easy to use and extremely configurable. The plugin allows you to bump the major, minor, patch or pre-release version based on the latest version, which is identified from a git tag. It also allows you to bump pre-release versions based on a scheme that you define. The version can be bumped by using version-component-specific project properties or can be bumped automatically based on the contents of a commit message. If no manual bumping is done via commit message or project property, the plugin will increment the version-component with the lowest precedence; this is usually the patch version, but can be the pre-release version if the latest version is a pre-release one. The plugin does its best to ensure that you do not accidentally violate semver rules while generating your versions; in cases where this might happen the plugin forces you to be explicit about violating these rules. As this is a settings plugin, it is applied to settings.gradle and version calculation is therefore performed right at the start of the build, before any projects are configured. This means that the project version is immediately available (almost as if it were set explicitly - which it effectively is), and will never change during the build (barring some other, external task that attempts to modify the version during the build). While the build is running, tagging or changing the project properties will not influence the version that was calculated at the start of the build.

(26 July 2018)