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 a61ff01784 Minor: Regenerated BOMs for
a084ed3ac9d04d0fb49369ee56883cada633e44a
omit a084ed3ac9 TOMEE-4663 - [tomee-10.x]: Bump
org.apache.geronimo.mail:geronimo-mail_2.1_provider from 1.1.0 to 1.1.1 (#3161)
add 142b4662da Minor: Regenerated BOMs for
0f4dd78ce56565de5fc4e0962cd9e75c26dbb9fc
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 (a61ff01784)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (142b4662da)
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/pom.xml | 2 +-
boms/tomee-plus/pom.xml | 2 +-
boms/tomee-webprofile/pom.xml | 2 +-
pom.xml | 2 +-
5 files changed, 5 insertions(+), 5 deletions(-)