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 9561223ec1 Minor: Regenerated BOMs for
98114cb92feaf369179ba3e4492750c3147c55db
add 31ccd360a1 [tomee-10.x]: Bump net.bytebuddy:byte-buddy from 1.18.11 to
1.18.14 (#2990)
add 2a9c6e221d TOMEE-4723 - [tomee-10.x]: Bump version.jackson from 2.22.2
to 2.22.3 (#2989)
add d64557c282 Minor: Regenerated BOMs for
2a9c6e221d790f058ae52f647a1c201a816b064e
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 (9561223ec1)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (d64557c282)
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 | 6 +++---
boms/tomee-plume/pom.xml | 6 +++---
boms/tomee-plus/pom.xml | 6 +++---
pom.xml | 2 +-
5 files changed, 11 insertions(+), 11 deletions(-)
