This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch regenerate_boms_after_dep_upgrade
in repository https://gitbox.apache.org/repos/asf/tomee.git
discard 5cb8dfdb01 Minor: Regenerated BOMs for
de50ddb492aa6c22c4574f14f43860a091dfc0ff
add bd4a7953c3 Bump version.arquillian from 1.10.0.Final to 1.10.1.Final
add bcb248e335 Minor: Regenerated BOMs for
bd4a7953c3eafc9d4a41ec45ab940b0fd2026673
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 (5cb8dfdb01)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(bcb248e335)
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/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 +-
5 files changed, 5 insertions(+), 5 deletions(-)
