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
omit a48a6b1d80 Minor: Regenerated BOMs for
13b4241c44d0329a027d95e9e729291a1f532006
add 5f81a8e6e3 TOMEE-4724 - Bump org.apache.neethi:neethi from 3.2.3 to
3.2.4 (#2988)
add 01f6c7b1a4 Minor: Regenerated BOMs for
5f81a8e6e394e7dd0cd87f78e42642eff795be51
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 (a48a6b1d80)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(01f6c7b1a4)
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(-)
