Search Gradle plugins
| Plugin | Latest Version |
|---|---|
to.wetransform.semantic-release-versionGradle plugin that determines the current version from a file with the last release version and information from Git. Intended to be used with semantic-release. |
2.1.2
(05 September 2024) |
com.mooltiverse.oss.nyxThe Nyx Gradle plugin automates the sematic release process for Gradle projects using semantic versioning and leveraging the Git branching model. |
3.0.11
(04 November 2024) |
to.wetransform.semantic-release-version-customGradle plugin that determines the current version based on information from Git and optionally a version file. Compared to the semantic-release-version plugin the behavior can be customized. |
2.1.2
(05 September 2024) |
io.github.serpro69.semantic-versioningThis plugin helps you to automatically version your gradle project according to semver rules |
0.14.0
(28 April 2024) |
de.gurkenlabs.semverguru"SemVerGuru" is your go-to Gradle plugin for effortless version management. Powered by Grgit and git describe, it seamlessly derives your project's version from Git tags. Take control of your versioning journey with easy Semantic Versioning increments, and with one-click git tag pushing. Keep it simple, stay semantic, and let SemVerGuru handle your project versions with ease. |
1.4
(31 December 2023) |
io.alcide.gradle-semantic-build-versioningThis 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) |
javamuc.gradle-semantic-build-versioningThis 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) |