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 0f55547f5c Minor: Regenerated BOMs for 
4e4e8e4d49831340c0da4e2fb4e79f806ec40865
     add 93541579fb TOMEE-4669 - Bump commons-codec:commons-codec from 1.22.0 
to 1.22.1 (#2875)
     add 26d953c263 Minor: Regenerated BOMs for 
93541579fb2a9a2cfb883dfca0ae229958b577e3

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   (0f55547f5c)
            \
             N -- N -- N   
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (26d953c263)

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-tomee-tests/arquillian-tomee-webprofile-tests/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                                                                 | 2 +-
 6 files changed, 6 insertions(+), 6 deletions(-)

Reply via email to