This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.apache.maven-maven-plugin-api-3.8.7
in repository https://gitbox.apache.org/repos/asf/logging-log4j-transform.git
discard 6a8c7d6 Bump maven-plugin-api from 3.6.0 to 3.8.7
add 4de2d59 Bump dependabot/fetch-metadata from 1.3.5 to 1.3.6 (#4)
add ca392bf Bump plexus-utils from 3.1.0 to 3.5.0 (#6)
add 0c0ea90 Bump maven-plugin-api from 3.6.0 to 3.8.7
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 (6a8c7d6)
\
N -- N -- N
refs/heads/dependabot/maven/org.apache.maven-maven-plugin-api-3.8.7 (0c0ea90)
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.yml | 2 +-
log4j-transform-parent/pom.xml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
