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 2edaaa961f Minor: Regenerated BOMs for
740fa88dd8a4bcedffd22403f2981a28825d951d
add 81e09331f4 TOMEE-4611 Bump tomcat.version from 10.1.54 to 10.1.55
(#2682)
add 77a07d6746 [tomee-10.x]: Bump version.arquillian from 1.10.1.Final to
1.10.2.Final
add 82412cdd7e Minor: Regenerated BOMs for
77a07d6746f6ed3b443132caadf0a9042625c2a8
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 (2edaaa961f)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (82412cdd7e)
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 | 4 ++--
tck/microprofile-tck/openapi/pom.xml | 2 +-
tck/microprofile-tck/opentelemetry/pom.xml | 2 +-
3 files changed, 4 insertions(+), 4 deletions(-)
