This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch
dependabot/maven/org.apache.logging.log4j-log4j-api-2.26.1
in repository https://gitbox.apache.org/repos/asf/maven.git
omit 3b4e3012a5 build: bump org.apache.logging.log4j:log4j-api from 2.23.1
to 2.26.1
add 0a37aa2fd0 Point ciManagement at GitHub Actions
add b46f9353aa Fix cycle match in ATR configuration
add c2107c26e3 Replace javax.annotation-api with jakarta.annotation-api
1.3.5
add 6ba724bb54 fix: strip version from test JARs in maven-classworlds to
avoid Dependabot failures (#13751)
add dad809df45 build: bump org.apache.logging.log4j:log4j-api from 2.23.1
to 2.26.1
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 (3b4e3012a5)
\
N -- N -- N
refs/heads/dependabot/maven/org.apache.logging.log4j-log4j-api-2.26.1
(dad809df45)
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:
.asf.yaml | 4 +++-
apache-maven/pom.xml | 4 ++--
apache-maven/src/main/appended-resources/META-INF/LICENSE.vm | 6 ++++--
impl/maven-classworlds/pom.xml | 1 +
.../src/test/test-data/optionally-existent.conf | 2 +-
.../src/test/test-data/valid-from-from-from.conf | 4 ++--
impl/maven-classworlds/src/test/test-data/valid.conf | 6 +++---
pom.xml | 12 ++++++------
src/graph/ReactorGraph.java | 2 +-
9 files changed, 23 insertions(+), 18 deletions(-)
