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

github-actions[bot] pushed a change to branch regenerate_boms_after_dep_upgrade
in repository https://gitbox.apache.org/repos/asf/tomee.git


 discard d6f7c18564 Minor: Regenerated BOMs for 
0ad6ecb31f12d4ec922495cb4b3ffce2a9938391
     add 86f2cc160b Minor: Regenerated BOMs for 
54e174a40304461537895c03e33c0785e9faa576 (#3167)
     add 8440a5dfdc Minor: Regenerated BOMs for 
86f2cc160b58c38bbffa6b638599ce0d027d6d35

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   (d6f7c18564)
            \
             N -- N -- N   refs/heads/regenerate_boms_after_dep_upgrade 
(8440a5dfdc)

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:

Reply via email to