This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/slf4j.version-2.0.2
in repository https://gitbox.apache.org/repos/asf/commons-vfs.git
discard 255e4194 Bump slf4j.version from 1.7.36 to 2.0.2
add 966f190d Bump maven-pmd-plugin from 3.18.0 to 3.19.0 (#304)
add d755bbc9 Bump maven-pmd-plugin from 3.18.0 to 3.19.0 #304
add d65fa2c3 Bump log4j2.version from 2.18.0 to 2.19.0 (#305)
add 617e2325 Bump log4j2.version from 2.18.0 to 2.19.0 #305
add 9ecb0eeb Bump junit-bom from 5.9.0 to 5.9.1 (#306)
add ac969d9f Bump slf4j.version from 1.7.36 to 2.0.2
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 (255e4194)
\
N -- N -- N refs/heads/dependabot/maven/slf4j.version-2.0.2
(ac969d9f)
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:
pom.xml | 2 +-
src/changes/changes.xml | 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
