This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/main/net.bytebuddy-byte-buddy-1.14.17
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git
discard 74f7493d5a Bump net.bytebuddy:byte-buddy from 1.14.16 to 1.14.17
add 9e7f4cbd97 Revert "Add `sync` option to all tabs"
add 3c72777ec7 Add `tabs-sync-option`
add 200d85a2f0 Update `net.bytebuddy:byte-buddy` to version `1.14.17`
(#2628)
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 (74f7493d5a)
\
N -- N -- N
refs/heads/dependabot/maven/main/net.bytebuddy-byte-buddy-1.14.17 (200d85a2f0)
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:
antora-playbook.yaml | 1 +
.../.3.x.x/update_net_bytebuddy_byte_buddy.xml | 4 ++--
.../antora/modules/ROOT/pages/manual/async.adoc | 4 ++--
.../modules/ROOT/pages/manual/configuration.adoc | 20 ++++++++---------
.../antora/modules/ROOT/pages/manual/filters.adoc | 2 +-
.../modules/ROOT/pages/manual/installation.adoc | 25 +++++++++++-----------
.../antora/modules/ROOT/pages/manual/scripts.adoc | 2 +-
7 files changed, 30 insertions(+), 28 deletions(-)
