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 30005196d0 Minor: Regenerated BOMs for
58f2efb9fa296b0c1f40f5429d5b1c1f7c8e193f
add 6600a4cbef Bump ch.qos.reload4j:reload4j from 1.2.26 to 1.2.27 (#3106)
add d327d4ee97 Minor: Regenerated BOMs for
6600a4cbef28907ab90c86b560d1a672fdf84c56
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 (30005196d0)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(d327d4ee97)
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 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
