Search Gradle plugins
| Plugin | Latest Version |
|---|---|
io.github.ben-manes.versions
CC-compatible
Gradle plugin that provides tasks for discovering dependency updates. |
0.66.0
(12 October 2026) |
io.github.ben-manes.versions.contributor
CC-compatible
Gradle plugin that contributes a project's dependency updates to the aggregate report. |
0.66.0
(12 October 2026) |
io.github.gmazzo.gitversion
CC-compatible
An opinionated Gradle version provider based on Git tags |
1.6.2
(27 September 2026) |
com.sneedit.deplens.settings
CC-compatible
Capture settings plugin versions and apply DepLens inventory, update checks and interactive edits to the root project. |
0.3.0
(25 October 2026) |
com.sneedit.deplens
CC-compatible
Gradle-native dependency, plugin and wrapper update checks with safe interactive version edits. |
0.3.0
(25 October 2026) |
io.github.khubaibkhan4
CC-compatible
Add, search, check and upgrade Kotlin Multiplatform dependencies from the command line: places each artifact in the right source set, writes the version catalog, KSP and plugins, and refuses libraries that don't support your targets. |
0.3.1
(16 October 2026) |
io.github.git-commit-id.git-commit-id-gradle-plugin
CC-compatible
Capture comprehensive git repository metadata at build time -- commit ID, branch, tags, and more -- to embed in your artifacts for reproducibility and traceability. |
0.0.1
(07 April 2026) |
|
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. |
4.2.2
(13 May 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. |
4.1.1
(26 July 2018) |
|
A simple versioning plugin that keeps track of build meta data!It can also update it's version from git and apply your version changes (such as increment to minor). |
1.1.1
(19 November 2019) |