This is an automated email from the ASF dual-hosted git repository.
ggregory 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 d71cf93 Prepare for the next release candidate
d71cf93 is described below
commit d71cf93030bcb529573b68168807e9cda89c3382
Author: Gary D. Gregory <garydgreg...@gmail.com>
AuthorDate: Sat Jan 25 21:45:31 2025 +0000
Prepare for the next release candidate
---
pom.xml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/pom.xml b/pom.xml
index c5f0001..d155ed0 100644
--- a/pom.xml
+++ b/pom.xml
@@ -25,7 +25,7 @@
</parent>
<groupId>org.apache.commons</groupId>
<artifactId>commons-parent</artifactId>
- <version>80-SNAPSHOT</version>
+ <version>80</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>2025-01-07T20:03:59Z</project.build.outputTimestamp>
+
<project.build.outputTimestamp>2025-01-25T21:41:15Z</project.build.outputTimestamp>
<commons.main.branch>master</commons.main.branch>
<commons.release.branch>release</commons.release.branch>
<commons.release.version>80</commons.release.version>
