This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.apache.maven.plugin-tools-maven-plugin-annotations-3.11.0
in repository https://gitbox.apache.org/repos/asf/logging-log4j-tools.git
omit d92cd66 Bump org.apache.maven.plugin-tools:maven-plugin-annotations
add 6f9b7b1 Bump apache/logging-parent from rel/10.5.0 to 10.6.0
add 41ec074 Bump `apache/logging-parent` workflow to version `10.6.0`
add 108086b Force `bnd-process` execution for Maven plugins
add 0cfa57a Expand wildcard imports
add a04092a Bump org.apache.maven.plugin-tools:maven-plugin-annotations
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 (d92cd66)
\
N -- N -- N
refs/heads/dependabot/maven/org.apache.maven.plugin-tools-maven-plugin-annotations-3.11.0
(a04092a)
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/workflows/build.yaml | 6 +++---
.github/workflows/merge-dependabot.yaml | 4 ++--
log4j-changelog-maven-plugin/pom.xml | 4 ++++
.../logging/log4j/changelog/exporter/ChangelogExporter.java | 9 ++++++++-
.../apache/logging/log4j/changelog/exporter/FreeMarkerUtils.java | 7 ++++++-
5 files changed, 23 insertions(+), 7 deletions(-)
