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 6a089e322d Minor: Regenerated BOMs for
6cbeacf4a4bf5286363ede6674008fa8ee40fd5c
omit 6cbeacf4a4 TOMEE-4672 - Bump org.bouncycastle:bcprov-jdk18on from 1.85
to 1.86 (#2998)
add d108fe43e3 Minor: Regenerated BOMs for
7399ef823376892ad051aafde4a2a6e1cf663537
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 (6a089e322d)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(d108fe43e3)
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 +-
server/openejb-cxf/pom.xml | 2 +-
5 files changed, 5 insertions(+), 5 deletions(-)
