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 9ece1d0074 Minor: Regenerated BOMs for 
ee8ff39f38865ca03808b42ebe60d6ec78a267fc
     add 762ba467f4 TOMEE-4663 - Bump 
org.apache.geronimo.mail:geronimo-mail_2.1_provider from 1.1.0 to 1.1.1 (#3160)
     add 43cbcf2024 Bump org.jacoco:jacoco-maven-plugin from 0.8.15 to 0.8.16 
(#3165)
     add 0ad6ecb31f Bump joda-time:joda-time from 2.15.0 to 2.15.1 (#3164)
     add d6f7c18564 Minor: Regenerated BOMs for 
0ad6ecb31f12d4ec922495cb4b3ffce2a9938391

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   (9ece1d0074)
            \
             N -- N -- N   refs/heads/regenerate_boms_after_dep_upgrade 
(d6f7c18564)

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-jaxws-tests/pom.xml       | 4 ++--
 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                                                               | 4 ++--
 6 files changed, 8 insertions(+), 8 deletions(-)

Reply via email to