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 dc0792dc03 Minor: Regenerated BOMs for
09f56ac353cc2dfbd215d398cc578d9e4f120530
add 55fe2465e2 TOMEE-4627 - Bump commons-logging:commons-logging from
1.3.6 to 1.4.0 (#2786)
add 2455a241f6 TOMEE-4629 - Bump com.sun.xml.messaging.saaj:saaj-impl
(#2785)
add 25cd69a511 Minor: Regenerated BOMs for
2455a241f6cb972ac76efc037274b408d30b1966
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 (dc0792dc03)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (25cd69a511)
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:
boms/tomee-microprofile/pom.xml | 4 ++--
boms/tomee-plume/pom.xml | 4 ++--
boms/tomee-plus/pom.xml | 4 ++--
boms/tomee-webprofile/pom.xml | 4 ++--
pom.xml | 4 ++--
5 files changed, 10 insertions(+), 10 deletions(-)
