This is an automated email from the ASF dual-hosted git repository.
kwin pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-release.git
The following commit(s) were added to refs/heads/master by this push:
new f0f28e5a Revert inclusion of ci skip in release commit msg
f0f28e5a is described below
commit f0f28e5ac0f1fd017239484ad0605e74be194e2b
Author: Rob Vesse <[email protected]>
AuthorDate: Mon Dec 8 15:01:18 2025 +0000
Revert inclusion of ci skip in release commit msg
This reverts PR #1423 which added the ci skip text into the default
release commit. This broke many developers workflows because it pushes
a choice about CI/CD process into default configuration. If developers
genuinely want to skip CI/CD for the release commit then they already
had configuration to override the commit message and inject the
necessary ci skip text. However, the maven-release-plugin itself should
not make any assumptions about developers CI/CD setups, nor do anything
by default that might cause those to skip release commit builds that
developers might be relying upon.
---
.../org/apache/maven/plugins/release/PrepareReleaseMojo.java | 12 ++----------
1 file changed, 2 insertions(+), 10 deletions(-)
diff --git
a/maven-release-plugin/src/main/java/org/apache/maven/plugins/release/PrepareReleaseMojo.java
b/maven-release-plugin/src/main/java/org/apache/maven/plugins/release/PrepareReleaseMojo.java
index 22fd08ef..4993d69d 100644
---
a/maven-release-plugin/src/main/java/org/apache/maven/plugins/release/PrepareReleaseMojo.java
+++
b/maven-release-plugin/src/main/java/org/apache/maven/plugins/release/PrepareReleaseMojo.java
@@ -281,18 +281,10 @@ public class PrepareReleaseMojo extends
AbstractScmReadWriteReleaseMojo {
* <li><code>artifactId</code> - The artifactId of the root project.
* <li><code>releaseLabel</code> - The release version of the root
project.
* </ul>
- * It is recommended to automatically skip this commit from the default
CI/CD build by including the string {@code ci skip}
- * in the commit message which is understood
- * by most CI systems, like <a
href="https://docs.github.com/en/actions/how-tos/manage-workflow-runs/skip-workflow-runs";>GitHub
Actions</a>,
- * <a href="https://docs.gitlab.com/ci/pipelines/#skip-a-pipeline";>GitLab
Pipelines</a>, and probably some more.
- * Otherwise the non-SNAPSHOT version is built again (outside the actual
release) and potentially also deployed somewhere
- * (which often leads to failed builds).
* @since 3.0.0-M1
*/
- @Parameter(
- defaultValue = "@{prefix} prepare release @{releaseLabel} [ci
skip]",
- property = "scmReleaseCommitComment")
- private String scmReleaseCommitComment = "@{prefix} prepare release
@{releaseLabel} [ci skip]";
+ @Parameter(defaultValue = "@{prefix} prepare release @{releaseLabel}",
property = "scmReleaseCommitComment")
+ private String scmReleaseCommitComment = "@{prefix} prepare release
@{releaseLabel}";
/**
* The SCM commit comment for the commit setting pom.xml back to
development version.
