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 9fed3f14c5 Minor: Regenerated BOMs for
900e87ccb3d3adb769e29e7e626322b8fb58a3fe
omit 900e87ccb3 TOMEE-4695 - [tomee-10.x]: Bump org.glassfish:jakarta.faces
from 4.0.26 to 4.0.27 (#3110)
omit 063dc57147 [tomee-10.x]: Bump ch.qos.reload4j:reload4j from 1.2.26 to
1.2.27 (#3104)
omit 3146f4bfe1 [tomee-10.x]: Bump version.asm from 9.10.1 to 9.11 (#3107)
add 621be5fab5 Minor: Regenerated BOMs for
d6ba2e99a098582fdbd91bbf643ffed30a860f7b
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 (9fed3f14c5)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (621be5fab5)
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 +-
mp-jwt/pom.xml | 2 +-
pom.xml | 4 ++--
4 files changed, 5 insertions(+), 5 deletions(-)
