Search Gradle plugins

Plugin Latest Version


This plugin automatically detects the current version of the project based on git tags. The plugin also provides helper tasks for printing the detected version and a list of all detected versions.

(25 February 2023)


Automaticall update gradle project version. Add tag and push to remote github repository.

(18 February 2023)


This extension will adjust the project version, based on current git branch or tag.

(17 February 2023)


Reckons the project version based on Git tags

(08 February 2023)


Manage project versions automatically with git tags

(04 January 2023)


Auto versioning based on the most recent git tag

(04 October 2022)


Plugin for creating git tag for release control

(14 September 2022)


Reads version from git tag, adds handler to read version in binary

(09 September 2022)


An easy way to tag build scans for Gradle plugin authors.

(03 August 2021)


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.

(13 May 2021)