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
omit 91e444efcc Minor: Regenerated BOMs for
f475de258fa3c498d6ca01669bb598b9d5d9cd1c
omit f475de258f Bump org.projectlombok:lombok from 1.18.42 to 1.18.46
omit 59b457d0fd Bump surefire.version from 3.5.5 to 3.5.6
add 33fd7f312b Minor: Regenerated BOMs for
9d27b18e152e335fdc2d486fd67574aa925cddad
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 (91e444efcc)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(33fd7f312b)
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:
pom.xml | 2 +-
tck/microprofile-tck/config/pom.xml | 2 +-
tck/microprofile-tck/fault-tolerance/pom.xml | 2 +-
tck/microprofile-tck/health/pom.xml | 2 +-
tck/microprofile-tck/jwt/pom.xml | 2 +-
tck/microprofile-tck/openapi/pom.xml | 2 +-
tck/microprofile-tck/opentelemetry/logs/pom.xml | 2 +-
tck/microprofile-tck/opentelemetry/metrics/pom.xml | 2 +-
tck/microprofile-tck/opentelemetry/tracing/pom.xml | 2 +-
tomee/apache-tomee/pom.xml | 2 +-
10 files changed, 10 insertions(+), 10 deletions(-)
