This is an automated email from the ASF dual-hosted git repository.

dependabot[bot] pushed a change to branch 
dependabot/maven/ch.qos.logback-logback-classic-1.6.4
in repository https://gitbox.apache.org/repos/asf/openmeetings.git


    omit 521d8c6e7 Bump ch.qos.logback:logback-classic from 1.6.3 to 1.6.4
     add 2ad2ea898 [OPENMEETINGS-2824] Bump de.thetaphi:forbiddenapis from 3.10 
to 3.11 (#306)
     add b75dcb455 [OPENMEETINGS-2824] Bump mockito.version from 5.23.0 to 
5.24.0 (#307)
     add 4df7596e8 [OPENMEETINGS-2824] Bump slf4j.version from 2.0.19 to 2.0.20 
(#308)
     add 8aad9729e [OPENMEETINGS-2824] Bump 
com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer (#309)
     add 6ee294966 [OPENMEETINGS-2824] Bump org.apache:apache from 39 to 40 
(#310)
     add 870d119d1 Bump ch.qos.logback:logback-classic from 1.6.3 to 1.6.4

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   (521d8c6e7)
            \
             N -- N -- N   
refs/heads/dependabot/maven/ch.qos.logback-logback-classic-1.6.4 (870d119d1)

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 | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

Reply via email to