This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch regenerate_boms_after_dep_upgrade
in repository https://gitbox.apache.org/repos/asf/tomee.git
omit 2665861672 Minor: Regenerated BOMs for
9965045eb79c0b2c8790d446989fb6dc75c18ebf
add 6147be25f6 Bump tomcat.version from 11.0.18 to 11.0.20
add 4bb5972100 Minor: Regenerated BOMs for
6147be25f6955b4c5ff90a7c2a0f6ae286c9ab8e
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 (2665861672)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(4bb5972100)
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 | 2 +-
5 files changed, 5 insertions(+), 5 deletions(-)
