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 969a3707f8 Minor: Regenerated BOMs for
284c8f0001952946610477ee69d7315d31386772
add 8d18cb6399 Minor: Regenerated BOMs for
db209094c4549195a7c3a877631c17034bc6bb95 (#2800)
add 8102d4ece7 Minor: Regenerated BOMs for
8d18cb6399ade59da3be39a419d3a6e7bd3595d8
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 (969a3707f8)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (8102d4ece7)
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:
