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 307e520350 Minor: Regenerated BOMs for
518e92bd8ea551c66fef2acb4d04a4abed50229e
add 7f418352bc TOMEE-4629 - Bump com.sun.xml.messaging.saaj:saaj-impl from
3.0.5 to 3.0.6 (#2788)
add 8a05dcfce7 Minor: Regenerated BOMs for
7f418352bc21a055cd094135b6b03f277ba20c90
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 (307e520350)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(8a05dcfce7)
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:
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 | 2 +-
5 files changed, 5 insertions(+), 5 deletions(-)
