This is an automated email from the ASF dual-hosted git repository.
github-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 f3833d5616 Minor: Regenerated BOMs for
bdf650bd9800f8010b954f90a2386a9684e1d4e2
add c0262e4a20 TOMEE-4597 Bump tomcat.version from 10.1.53 to 10.1.54
(#2583)
add bc4001d63e Minor: Regenerated BOMs for
c0262e4a20890ef16e61de4d68ff015a54722e15
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 (f3833d5616)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (bc4001d63e)
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 +-
1 file changed, 1 insertion(+), 1 deletion(-)
