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
discard 3cf79412a8 Minor: Regenerated BOMs for
65f43fb8a0b9a0b4528ad6f2d54a5c78297f1990
add 0415279860 [tomee-10.x]: Bump org.projectlombok:lombok from 1.18.44 to
1.18.46
add 22c77dd633 [tomee-10.x]: Bump org.jboss.arquillian:arquillian-bom
add c7f3f82d1d [tomee-10.x]: Bump version.hibernate.orm
add c9b99e356d TOMEE-4618 - SAAJ 3.0.5
add 12fae0117e Minor: Regenerated BOMs for
c9b99e356d7abb5b206613eaeb52ea470b001441
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 (3cf79412a8)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (12fae0117e)
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:
arquillian/functional-tests/spring-cxf-tomee-4332/pom.xml | 2 +-
boms/tomee-microprofile/pom.xml | 2 +-
boms/tomee-plume/pom.xml | 2 +-
boms/tomee-plus/pom.xml | 2 +-
boms/tomee-webprofile/pom.xml | 2 +-
pom.xml | 6 +++---
tomee/apache-tomee/pom.xml | 2 +-
7 files changed, 9 insertions(+), 9 deletions(-)
