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 c22d71ba6d Minor: Regenerated BOMs for
aadefa28fddf6689fbdea1ffff52027a3b32bb6c
add 88a1e0696e [tomee-10.x]: Bump
org.hibernate.validator:hibernate-validator
add c94995dabb Minor: Regenerated BOMs for
88a1e0696ee2a9b20cd57d45226580635fda7492
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 (c22d71ba6d)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (c94995dabb)
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(-)
