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
omit 684f013ad3 Minor: Regenerated BOMs for
5058ab21cb853868fd54490fdc4b3f4ad2343b30
add 98114cb92f TOMEE-4725 - [tomee-10.x]: Bump version.wss4j from 4.0.1 to
4.0.2 (#2993)
add 31ccd360a1 [tomee-10.x]: Bump net.bytebuddy:byte-buddy from 1.18.11 to
1.18.14 (#2990)
add 5d201dffa6 Minor: Regenerated BOMs for
31ccd360a13d9fe1f687efced63625235e8d5c80
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 (684f013ad3)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (5d201dffa6)
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:
arquillian/arquillian-tomee-tests/pom.xml | 2 +-
boms/tomee-microprofile/pom.xml | 65 +++++++++++++++++++------------
boms/tomee-plume/pom.xml | 65 +++++++++++++++++++------------
boms/tomee-plus/pom.xml | 65 +++++++++++++++++++------------
boms/tomee-webprofile/pom.xml | 29 ++++++++++----
pom.xml | 2 +-
6 files changed, 144 insertions(+), 84 deletions(-)
