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 3c29a0b0ec Minor: Regenerated BOMs for
b38607c0c53d88027d3cc754ea6ef2537677da25
add 8fd6500627 TOMEE-4565 Bump org.glassfish:jakarta.faces from 4.0.13 to
4.0.14 (#2425)
add c83575b5d5 Minor: Regenerated BOMs for
8fd6500627f1a165ef196a03b337f9b97a8228bc
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 (3c29a0b0ec)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (c83575b5d5)
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 | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
