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 6028e911ac Minor: Regenerated BOMs for
18037a4245a276ccb33ced4e44ad46fe53dae924
add 4012fa5983 TOMEE-4615 - Mojarra 4.0.18
add d6aae7b3cf Minor: Regenerated BOMs for
4012fa5983ccee90d1875bc5586311dfe5ba4093
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 (6028e911ac)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (d6aae7b3cf)
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(-)
