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 18bea1c7d6 Minor: Regenerated BOMs for
8a9ce3a7a0c62dc5969d59b5e0c3da42496351c0
add 24837fbf52 TOMEE-4720 - [tomee-10.x]: Bump org.yaml:snakeyaml from 2.6
to 2.7 (#2973)
add 3dda9df704 Minor: Regenerated BOMs for
24837fbf52490c17484c0e03116ed8557e99ac90
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 (18bea1c7d6)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (3dda9df704)
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 +-
pom.xml | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
