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 4425f1af53 Minor: Regenerated BOMs for
6125f8f501068e523f77f1be68c69cf57c4d7a59
add 312caa49ae TOMEE-4672 - Bump org.bouncycastle:bcpkix-jdk18on from 1.85
to 1.86 (#3045)
add a3b37fd88f Minor: Regenerated BOMs for
312caa49ae722d81fea43f686f1fb08f6487d217
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 (4425f1af53)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(a3b37fd88f)
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 ++--
server/openejb-cxf/pom.xml | 2 +-
5 files changed, 9 insertions(+), 9 deletions(-)
