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 eeda875 Prepare for the next release candidate eeda875 is described below commit eeda875f9008c0feb820f58c08697ea2efd48334 Author: Gary D. Gregory <garydgreg...@gmail.com> AuthorDate: Wed Jan 29 16:24:14 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 2873b9e..8e7276b 100644 --- a/pom.xml +++ b/pom.xml @@ -25,7 +25,7 @@ </parent> <groupId>org.apache.commons</groupId> <artifactId>commons-parent</artifactId> - <version>81-SNAPSHOT</version> + <version>81</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-29T12:23:24Z</project.build.outputTimestamp> + <project.build.outputTimestamp>2025-01-29T16:19:20Z</project.build.outputTimestamp> <commons.main.branch>master</commons.main.branch> <commons.release.branch>release</commons.release.branch> <commons.release.version>81</commons.release.version>