This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/2.x/org.apache.tomcat-tomcat-juli-10.0.27
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git
omit a3d8075e9f Bump tomcat-juli from 10.0.23 to 10.0.27
add 9146e99a38 Bump docker-maven-plugin from 0.40.2 to 0.42.0 (#1350)
add 63ab6796be Bump maven-core from 3.8.6 to 3.9.0 (#1351)
add 998cffecc6 Revert Maven from 3.9.0 back to 3.8.7
add 30e29899cb Bump tomcat-juli from 10.0.23 to 10.0.27
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 (a3d8075e9f)
\
N -- N -- N
refs/heads/dependabot/maven/2.x/org.apache.tomcat-tomcat-juli-10.0.27
(30e29899cb)
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:
.mvn/wrapper/maven-wrapper.properties | 2 +-
pom.xml | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
