[prev in list] [next in list] [prev in thread] [next in thread] 

List:       flume-commits
Subject:    (logging-log4j-jakarta) branch dependabot/maven/org.springframework-spring-framework-bom-6.1.7 updat
From:       github-bot () apache ! org
Date:       2024-05-16 20:31:17
Message-ID: 171589147769.1413991.14188489729578911614 () gitbox2-he-fi ! apache ! org
[Download RAW message or body]

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

github-bot pushed a change to branch \
dependabot/maven/org.springframework-spring-framework-bom-6.1.7 in repository \
https://gitbox.apache.org/repos/asf/logging-log4j-jakarta.git


 discard 8810b9a  Bump org.springframework:spring-framework-bom from 6.1.5 to 6.1.7
     add 74b8fea  Update `org.springframework:spring-framework-bom` to version \
`6.1.7` (#30)

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   (8810b9a)
            \
             N -- N -- N   \
refs/heads/dependabot/maven/org.springframework-spring-framework-bom-6.1.7 (74b8fea)

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:
 .../.3.x.x/update_org_springframework_spring_framework_bom.xml        | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)


[prev in list] [next in list] [prev in thread] [next in thread]