Conventional Commits for the Maven Release Plugin

Introduction

When using the maven-release-plugin you can add custom rules on how the next version is determined. Such a “next version calculation” is called a Version Policy.

This is a version policy that enforces the Semantic Versioning format and upgrades major/minor/patch element for next development version depending on the commit messages since the previous release which is detected by looking at the tags in the SCM.

The default configuration follows the Conventional Commits standard for calculating the next version.

Requirements

This version policy requires version 3.0.0 or newer of the maven-release-plugin to be used.

How the next version is calculated

The calculation works as follows:

Current version:

It tries to find the previously released version by searching for the previous release tag.

Here the configured versionTag regex is used to locate and extract (the regex MUST have exactly 1 capture group) the correct value.
If no matching tags are found the project version from the pom.xml is used as the fallback reference point.

Next release version:

Notation used:

? : the new version element is the same as the existing version element.
+1: the new version element is the existing version element + 1.
0 : the new version element is 0.

The steps:

By default, it assumes that only a patch release (i.e. ?.?.+1 ) is needed.
If any of the commit messages since the previous release tag match any of the of minorRules regexes then it assumes the next release is a minor release (i.e. ?.+1.0 ).
If any of the commit messages since the previous release tag match any of the of majorRules regexes then it assumes the next release is a major release (i.e. +1.0.0 ).

Next development version:

The next development version is always calculated as the next release version and then ?.?.+1-SNAPSHOT.

Examining what is happening:

When doing mvn release:prepare -X the details about the found tags, commit messages and the used patterns are output to the console.

Configuration

Default configuration

The default configuration assumes a version tag that is just the version (i.e. something like 1.2.3) and the rules from the Conventional Commits v1.0.0 are followed.

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-release-plugin</artifactId>
  <version>3.0.0</version>
  <dependencies>
    <dependency>
      <groupId>nl.basjes.maven.release</groupId>
      <artifactId>conventional-commits-version-policy</artifactId>
      <version>1.0.6</version>
    </dependency>
  </dependencies>
  <configuration>
    <projectVersionPolicyId>ConventionalCommitsVersionPolicy</projectVersionPolicyId>
  </configuration>
</plugin>

Using a custom release tag format

If you want a different tag format this will usually result in setting it both when creating the tag and for finding it again. Here the rules from the Conventional Commits v1.0.0 are also followed.

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-release-plugin</artifactId>
  <version>3.0.0</version>
  <dependencies>
    <dependency>
      <groupId>nl.basjes.maven.release</groupId>
      <artifactId>conventional-commits-version-policy</artifactId>
      <version>1.0.6</version>
    </dependency>
  </dependencies>
  <configuration>
    <tagNameFormat>v@{project.version}</tagNameFormat>

    <projectVersionPolicyId>ConventionalCommitsVersionPolicy</projectVersionPolicyId>

    <!-- projectVersionPolicyConfig for the ConventionalCommitsVersionPolicy is an XML structure:  -->
    <projectVersionPolicyConfig>
      <!-- versionTag: A regex with 1 capture group that MUST extract the project.version from the SCM tag. -->
      <versionTag>^v([0-9]+\.[0-9]+\.[0-9]+)$</versionTag>
    </projectVersionPolicyConfig>
  </configuration>
</plugin>

Using custom commit message patterns

If either the minor or major rules are specified then all default rules (both minor and major) are dropped in favour of the configuration.

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-release-plugin</artifactId>
  <version>3.0.0</version>
  <dependencies>
    <dependency>
      <groupId>nl.basjes.maven.release</groupId>
      <artifactId>conventional-commits-version-policy</artifactId>
      <version>1.0.6</version>
    </dependency>
  </dependencies>
  <configuration>
    <tagNameFormat>v@{project.version}</tagNameFormat>

    <projectVersionPolicyId>ConventionalCommitsVersionPolicy</projectVersionPolicyId>

    <!-- projectVersionPolicyConfig for the ConventionalCommitsVersionPolicy is an XML structure:  -->
    <projectVersionPolicyConfig>
      <!-- versionTag: A regex with 1 capture group that MUST extract the project.version from the SCM tag. -->
      <versionTag>^v([0-9]+\.[0-9]+\.[0-9]+)$</versionTag>
      <!-- majorRules: A list regexes that will be matched against all lines in each commit message since   -->
      <!--             the last tag. If matched the next version is at least a MAJOR update.                -->
      <majorRules>
        <majorRule>^[a-zA-Z]+(?:\([a-zA-Z0-9_-]+\))?!: .*$</majorRule>
        <majorRule>^BREAKING CHANGE:.*$</majorRule>
      </majorRules>
      <!-- minorRules: A list regexes that will be matched against all lines in each commit message since   -->
      <!--             the last tag. If matched the next version is at least a MINOR update.                -->
      <minorRules>
        <minorRule>^feat(?:\([a-zA-Z0-9_-]+\))?: .*$</minorRule>
      </minorRules>
    </projectVersionPolicyConfig>
  </configuration>
</plugin>

License

Conventional Commits Version Policy
Copyright (C) 2022-2024 Niels Basjes

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

https://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.