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


 discard 2f9f2497a6 Minor: Regenerated BOMs for 
8e1bc25cccf64d92777f81627709c350bbe6369f
     add fef387e376 Bump com.google.code.gson:gson from 2.14.0 to 2.15.0 (#3149)
     add 409a8e7aae Bump org.apache.axis2:axis2-saaj from 1.8.2 to 2.0.2 (#3147)
     add 97c2bbe49a Bump version.hibernate.orm from 7.4.13.Final to 
7.4.14.Final (#3133)
     add a8db17a684 Minor: Regenerated BOMs for 
97c2bbe49afbe1b1f755bafdb4d7fd1b8ea40c57

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   (2f9f2497a6)
            \
             N -- N -- N   refs/heads/regenerate_boms_after_dep_upgrade 
(a8db17a684)

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:
 pom.xml                            | 4 ++--
 server/openejb-webservices/pom.xml | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

Reply via email to