This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/main/io.netty-netty-bom-4.1.103.Final
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git
omit deb7e9f2a6 Bump io.netty:netty-bom from 4.1.101.Final to 4.1.103.Final
add 6ad835c171 Update `org.apache.tomcat:tomcat-juli` to version `10.1.17`
(#2086)
add 2e08dc2d1e Update
`org.elasticsearch.client:elasticsearch-rest-high-level-client` to version
`7.17.16` (#2085)
add 3bfe27f7ec Update `io.netty:netty-bom` to version `4.1.102.Final`
(#2084)
add ac46435fe0 Bump io.netty:netty-bom from 4.1.101.Final to 4.1.103.Final
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 (deb7e9f2a6)
\
N -- N -- N
refs/heads/dependabot/maven/main/io.netty-netty-bom-4.1.103.Final (ac46435fe0)
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:
log4j-parent/pom.xml | 4 ++--
src/changelog/.3.x.x/update_io_netty_netty_bom.xml | 4 ++--
src/changelog/.3.x.x/update_org_apache_tomcat_tomcat_juli.xml | 4 ++--
..._org_elasticsearch_client_elasticsearch_rest_high_level_client.xml | 4 ++--
4 files changed, 8 insertions(+), 8 deletions(-)
