This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/2.x/io.netty-netty-bom-4.1.100.Final
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git
discard c1e0b066ca Bump io.netty:netty-bom from 4.1.97.Final to 4.1.100.Final
add dd98dd09d7 Fix Dependabot workflow
add 360cd14676 LMAX Disruptor requires Java 11
add a73c4fa680 Fix typo
add d25b7f0847 Bump io.netty:netty-bom from 4.1.97.Final to 4.1.100.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 (c1e0b066ca)
\
N -- N -- N
refs/heads/dependabot/maven/2.x/io.netty-netty-bom-4.1.100.Final (d25b7f0847)
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:
.github/dependabot.yml | 13 ++++++++-----
.github/workflows/merge-dependabot.yaml | 4 ++--
2 files changed, 10 insertions(+), 7 deletions(-)
