This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.slf4j-slf4j-log4j12-1.7.33
in repository https://gitbox.apache.org/repos/asf/commons-vfs.git.
discard 8d60114 Bump slf4j-log4j12 from 1.5.11 to 1.7.33
add 9d8a62c Remove extra whitespace.
add 5c6e16f Bump actions/cache from 2.1.7 to 3 (#249)
add 227b9cb Bump actions/cache from 2.1.7 to 3 #249
add b34a5eb Bump slf4j.version from 1.7.26 to 1.7.36 (#244)
add 16796cd Bump slf4j.version from 1.7.26 to 1.7.36 #244
add 50f1d2e Bump slf4j-log4j12 from 1.5.11 to 1.7.33
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 (8d60114)
\
N -- N -- N
refs/heads/dependabot/maven/org.slf4j-slf4j-log4j12-1.7.33 (50f1d2e)
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/maven.yml | 2 +-
commons-vfs2-jackrabbit1/pom.xml | 4 ++--
.../main/java/org/apache/commons/vfs2/cache/DefaultFilesCache.java | 2 --
pom.xml | 2 +-
src/changes/changes.xml | 5 ++++-
5 files changed, 8 insertions(+), 7 deletions(-)
