This is an automated email from the ASF dual-hosted git repository.
garydgregory pushed a commit to branch release
in repository https://gitbox.apache.org/repos/asf/commons-parent.git
The following commit(s) were added to refs/heads/release by this push:
new 9066f72 Prepare for the release candidate 104 RC1
9066f72 is described below
commit 9066f72892fba9af187520ba37889ae068a333ba
Author: Gary Gregory <[email protected]>
AuthorDate: Thu Aug 20 14:24:25 2026 +0000
Prepare for the release candidate 104 RC1
---
pom.xml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/pom.xml b/pom.xml
index 8152377..ec59130 100644
--- a/pom.xml
+++ b/pom.xml
@@ -25,7 +25,7 @@
</parent>
<groupId>org.apache.commons</groupId>
<artifactId>commons-parent</artifactId>
- <version>104-SNAPSHOT</version>
+ <version>104</version>
<packaging>pom</packaging>
<name>Apache Commons Parent</name>
<description>The Apache Commons Parent POM provides common settings for all
Apache Commons components.</description>
@@ -73,7 +73,7 @@
<!-- configuration bits for cutting a release candidate, must be
overridden by components -->
<!-- TODO How can we make project.build.outputTimestamp and changes.xml's
release data the same? -->
<!-- project.build.outputTimestamp is managed by Maven plugins, see
https://maven.apache.org/guides/mini/guide-reproducible-builds.html -->
-
<project.build.outputTimestamp>2026-07-21T21:56:10Z</project.build.outputTimestamp>
+
<project.build.outputTimestamp>2026-08-20T14:23:47Z</project.build.outputTimestamp>
<commons.main.branch>master</commons.main.branch>
<commons.release.branch>release</commons.release.branch>
<commons.release.version>104</commons.release.version>
