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
omit 9a1fb86b2c Minor: Regenerated BOMs for
063dc57147c3f6c14cce6673f9aade4214cc32f3
add 900e87ccb3 TOMEE-4695 - [tomee-10.x]: Bump org.glassfish:jakarta.faces
from 4.0.26 to 4.0.27 (#3110)
add b0d9dd1508 [tomee-10.x]: Bump
org.hibernate.validator:hibernate-validator from 8.0.5.Final to 8.0.6.Final
(#3111)
add 100377c8f8 Minor: Regenerated BOMs for
b0d9dd1508f43e942aae17ef1889488c67d487ea
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 (9a1fb86b2c)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (100377c8f8)
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:
boms/tomee-plume-api/pom.xml | 2 +-
boms/tomee-plume/pom.xml | 2 +-
pom.xml | 4 ++--
3 files changed, 4 insertions(+), 4 deletions(-)
