This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/org.junit-junit-bom-6.0.3
in repository https://gitbox.apache.org/repos/asf/commons-parent.git
discard 37be1d4 Bump org.junit:junit-bom from 5.14.2 to 6.0.3
add 21154ca Bump com.puppycrawl.tools:checkstyle from 13.2.0 to 13.4.0 on
Java 21 and up
add 88f7e44 Bump commons.rat.version from 0.17.0 to 0.18 on Java 17 and up
add 59ec22a Prepare for the next release candidate
add cd07530 Prepare for the release candidate 98 RC1
add fff40bd Bump to next development version
add 9516ce0 Updates for the next release
add b7085b4 Updates for the next release
add 5c4df12 Bump com.github.siom79.japicmp:japicmp-maven-plugin from
0.25.4 to 0.25.5
add 26b695e Bump minimalMavenBuildVersion from 3.8.1 to 3.9
add a2611b4 Bump commons.junit.version from 5.14.2 to 5.14.3.
add a206294 Bump org.junit:junit-bom from 5.14.2 to 6.0.3
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (37be1d4)
\
N -- N -- N
refs/heads/dependabot/maven/org.junit-junit-bom-6.0.3 (a206294)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
README.md | 4 ++--
RELEASE-NOTES.txt | 31 +++++++++++++++++++++++++++++++
pom.xml | 17 +++++++++--------
src/changes/changes.xml | 12 +++++++++++-
4 files changed, 53 insertions(+), 11 deletions(-)
