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_tomee-10.x
in repository https://gitbox.apache.org/repos/asf/tomee.git
omit 100377c8f8 Minor: Regenerated BOMs for
b0d9dd1508f43e942aae17ef1889488c67d487ea
add 8f6b811e29 Minor: Regenerated BOMs for
3146f4bfe1b53306bfaee2d01a49ac850589a745 (#3113)
add 35b0e8d0b3 Minor: Regenerated BOMs for
8f6b811e29df870ed797cbb9b05054e5b7de057e
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 (100377c8f8)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (35b0e8d0b3)
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:
