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 87f11e1b77 Minor: Regenerated BOMs for 
191773a55c269275bfd708382397e1850ddd3743
     add 4444369bfc Bump org.jboss.shrinkwrap.resolver:shrinkwrap-resolver-bom
     add bdf1cfaae6 Minor: Regenerated BOMs for 
4444369bfcbd82782bf3eb59be92ae7ea1f86f07

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   (87f11e1b77)
            \
             N -- N -- N   refs/heads/regenerate_boms_after_dep_upgrade 
(bdf1cfaae6)

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/functional-tests/spring-cxf-tomee-4332/pom.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Reply via email to