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 30e0ee2b9d Minor: Regenerated BOMs for
37519fe865644b6749cf19257ebb10575551df68
add 9a8ea1c189 TOMEE-4599 Bump org.glassfish:jakarta.faces from 4.0.14 to
4.0.15 (#2589)
add dc0a0ec273 [tomee-10.x]: Bump org.jboss.logging:jboss-logging
add 19f3808608 Minor: Regenerated BOMs for
dc0a0ec273c8e4dac192dc0da17ba0d9a7dcd2af
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 (30e0ee2b9d)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (19f3808608)
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-microprofile/pom.xml | 2 +-
boms/tomee-plume-api/pom.xml | 2 +-
boms/tomee-plume/pom.xml | 4 ++--
boms/tomee-plus/pom.xml | 2 +-
pom.xml | 4 ++--
5 files changed, 7 insertions(+), 7 deletions(-)
