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 7b493514b7 Minor: Regenerated BOMs for 
0415279860b018e2c87ebb762969f2e44202dc5f
     add 22c77dd633 [tomee-10.x]: Bump org.jboss.arquillian:arquillian-bom
     add c7f3f82d1d [tomee-10.x]: Bump version.hibernate.orm
     add c9b99e356d TOMEE-4618 - SAAJ 3.0.5
     add 2ecbdd9e79 [tomee-10.x]: Bump actions/checkout from 6.0.2 to 6.0.3
     add 2adbe1c7a2 Minor: Regenerated BOMs for 
2ecbdd9e79cdc6d52f7fac05bafb42de90526c28

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   (7b493514b7)
            \
             N -- N -- N   
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (2adbe1c7a2)

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:
 .github/workflows/main-pull-request-build.yml             | 2 +-
 .github/workflows/main-push-build.yml                     | 2 +-
 arquillian/functional-tests/spring-cxf-tomee-4332/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                                                   | 6 +++---
 8 files changed, 10 insertions(+), 10 deletions(-)

Reply via email to