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 82e6cad085 Minor: Regenerated BOMs for
308f5b8e0d49b30b11605abc39871b5711f8da94
add bd542b8d4c [tomee-10.x]: Bump org.codehaus.mojo:jaxb2-maven-plugin
from 4.1.0 to 4.2.0 (#3005)
add a0e8e29a4c TOMEE-4722 - [tomee-10.x]: Bump version.slf4j from 2.0.18
to 2.0.20 (#3003)
add 99e1d0d2b2 Minor: Regenerated BOMs for
a0e8e29a4c5b5a28576c3b7d487a509fbe60f541
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 (82e6cad085)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (99e1d0d2b2)
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 ++--
pom.xml | 4 ++--
5 files changed, 10 insertions(+), 10 deletions(-)
