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 4e875e330d Minor: Regenerated BOMs for
98e9247dff81469b2594598128263478219916af
add 09f56ac353 TOMEE-4626 - Bump tomcat.version from 10.1.55 to 10.1.56
(#2772)
add 55fe2465e2 TOMEE-4627 - Bump commons-logging:commons-logging from
1.3.6 to 1.4.0 (#2786)
add b4f8fd2cec Minor: Regenerated BOMs for
55fe2465e24cc85c362a4263b6c0b3aafc29b520
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 (4e875e330d)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (b4f8fd2cec)
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 | 2 +-
boms/tomee-plume/pom.xml | 2 +-
boms/tomee-plus/pom.xml | 2 +-
boms/tomee-webprofile/pom.xml | 2 +-
pom.xml | 4 ++--
5 files changed, 6 insertions(+), 6 deletions(-)
