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 c12b1b6 Prepare for the release candidate 91 RC1
c12b1b6 is described below
commit c12b1b62a590decf27aa26ea3df08f02e8318a96
Author: Gary Gregory <[email protected]>
AuthorDate: Fri Nov 7 20:25:43 2025 +0000
Prepare for the release candidate 91 RC1
---
CONTRIBUTING.md | 2 +-
README.md | 4 ++--
pom.xml | 4 ++--
3 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 5602514..452b10c 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -69,7 +69,7 @@ Making Changes
+ Respect the original code style:
+ Only use spaces for indentation; you can check for unnecessary whitespace
with `git diff` before committing.
+ Create minimal diffs - disable _On Save_ actions like _Reformat Source
Code_ or _Organize Imports_. If you feel the source code should be reformatted
create a separate PR for this change first.
-+ Write unit tests that match behavioral changes, where the tests fail if the
changes to the runtime are not applied. This may not always be possible but is
a best practice.
++ Write unit tests that match behavioral changes, where the tests fail if the
changes to the runtime are not applied. This may not always be possible but is
a best-practice.
Unit tests are typically in the `src/test/java` directory.
+ Run a successful build using the default [Maven](https://maven.apache.org/)
goal with `mvn`; that's `mvn` on the command line by itself.
+ Write a pull request description that is detailed enough to understand what
the pull request does, how, and why.
diff --git a/README.md b/README.md
index 2d381f5..6194d19 100644
--- a/README.md
+++ b/README.md
@@ -45,7 +45,7 @@ Apache Commons Parent
[](https://github.com/apache/commons-parent/actions/workflows/maven.yml)
[](https://search.maven.org/artifact/org.apache.commons/commons-parent)
-[](https://javadoc.io/doc/org.apache.commons/commons-parent/91)
+[](https://javadoc.io/doc/org.apache.commons/commons-parent/92)
[](https://github.com/apache/commons-parent/actions/workflows/codeql-analysis.yml)
[](https://api.securityscorecards.dev/projects/github.com/apache/commons-parent)
@@ -68,7 +68,7 @@ Alternatively, you can pull it from the central Maven
repositories:
<dependency>
<groupId>org.apache.commons</groupId>
<artifactId>commons-parent</artifactId>
- <version>91</version>
+ <version>92</version>
</dependency>
```
diff --git a/pom.xml b/pom.xml
index 9a65548..6d181c4 100644
--- a/pom.xml
+++ b/pom.xml
@@ -25,7 +25,7 @@
</parent>
<groupId>org.apache.commons</groupId>
<artifactId>commons-parent</artifactId>
- <version>92-SNAPSHOT</version>
+ <version>91</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-10-30T11:20:50Z</project.build.outputTimestamp>
+
<project.build.outputTimestamp>2025-11-07T20:25:03Z</project.build.outputTimestamp>
<commons.main.branch>master</commons.main.branch>
<commons.release.branch>release</commons.release.branch>
<commons.release.version>92</commons.release.version>
