This is an automated email from the ASF dual-hosted git repository.

github-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 ae472cb1af Minor: Regenerated BOMs for 
fe15c310f8b4ee1303e02fcc9bf2a148fe5cbb42
     add 06ac2dd450 TOMEE-2421 Bump version.microprofile.impl.config (#2421)
     add 34bd7ea6e9 Minor: Regenerated BOMs for 
69530f4e413801fd0c0200620114070fc2c6c0f6 (#2433)
     add 48bd4e0728 Minor: Regenerated BOMs for 
34bd7ea6e916c8872637c68f13c8123f1a70eacb

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   (ae472cb1af)
            \
             N -- N -- N   
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (48bd4e0728)

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 | 16 ++++++++--------
 boms/tomee-plume/pom.xml        | 16 ++++++++--------
 boms/tomee-plus/pom.xml         | 16 ++++++++--------
 pom.xml                         |  2 +-
 4 files changed, 25 insertions(+), 25 deletions(-)

Reply via email to