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
discard 830de7c20d Minor: Regenerated BOMs for
cce5ef222e84c6eb89b2b20effe1d06ba6cba70d
add 9d27b18e15 Bump net.bytebuddy:byte-buddy from 1.18.9 to 1.18.10
add 59b457d0fd Bump surefire.version from 3.5.5 to 3.5.6
add f475de258f Bump org.projectlombok:lombok from 1.18.42 to 1.18.46
add 58d247d292 Bump org.codehaus.gmavenplus:gmavenplus-plugin from 4.3.1
to 5.0.0
add e59634c2f4 Minor: Regenerated BOMs for
58d247d292c86c9af4174c00381cdb953117745e
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 (830de7c20d)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(e59634c2f4)
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 +-
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 +-
tomee/tomee-webaccess/pom.xml | 2 +-
12 files changed, 12 insertions(+), 12 deletions(-)
