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 1ed2338  Prepare for the release candidate 106 RC1
1ed2338 is described below

commit 1ed23384ceabd651bba59cd28890cf303ce17eee
Author: Gary Gregory <[email protected]>
AuthorDate: Tue Oct 13 22:11:07 2026 +0000

    Prepare for the release candidate 106 RC1
---
 pom.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/pom.xml b/pom.xml
index dd226a1..99baaf3 100644
--- a/pom.xml
+++ b/pom.xml
@@ -25,7 +25,7 @@
   </parent>
   <groupId>org.apache.commons</groupId>
   <artifactId>commons-parent</artifactId>
-  <version>106-SNAPSHOT</version>
+  <version>106</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-09-07T12:29:12Z</project.build.outputTimestamp>
+    
<project.build.outputTimestamp>2026-10-13T22:10:24Z</project.build.outputTimestamp>
     <commons.main.branch>master</commons.main.branch>
     <commons.release.branch>release</commons.release.branch>
     <commons.release.version>106</commons.release.version>

Reply via email to