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 99e1d0d2b2 Minor: Regenerated BOMs for 
a0e8e29a4c5b5a28576c3b7d487a509fbe60f541
     add df8e103c55 TOMEE-4672 - [tomee-10.x]: Bump 
org.bouncycastle:bcprov-jdk18on from 1.85 to 1.86 (#3002)
     add af3a99a22e Minor: Regenerated BOMs for 
df8e103c55d87711ab446923ad35574aec7a1468

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   (99e1d0d2b2)
            \
             N -- N -- N   
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (af3a99a22e)

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 +-
 server/openejb-cxf/pom.xml      | 2 +-
 5 files changed, 5 insertions(+), 5 deletions(-)

Reply via email to