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 f26020f Prepare for the release candidate 105 RC1
f26020f is described below
commit f26020f05ae7e5f87f43f24cf59f76f259e8569e
Author: Gary Gregory <[email protected]>
AuthorDate: Fri Sep 4 12:19:53 2026 +0000
Prepare for the release candidate 105 RC1
---
pom.xml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/pom.xml b/pom.xml
index 97a7d9a..ab74ae8 100644
--- a/pom.xml
+++ b/pom.xml
@@ -25,7 +25,7 @@
</parent>
<groupId>org.apache.commons</groupId>
<artifactId>commons-parent</artifactId>
- <version>105-SNAPSHOT</version>
+ <version>105</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-08-22T11:29:02Z</project.build.outputTimestamp>
+
<project.build.outputTimestamp>2026-09-04T12:19:06Z</project.build.outputTimestamp>
<commons.main.branch>master</commons.main.branch>
<commons.release.branch>release</commons.release.branch>
<commons.release.version>105</commons.release.version>
