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
in repository https://gitbox.apache.org/repos/asf/tomee.git
omit 2cd8ba0f64 Minor: Regenerated BOMs for
7c49ef0200ce0ff7fc096e8ca91ce5e8f19202ca
add 5003bfef17 TOMEE-4668 - SmallRye Config 3.18.1
add 16dcff980c Minor: Regenerated BOMs for
5003bfef175eb4e8442a0eaf204687768e11e451
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 (2cd8ba0f64)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(16dcff980c)
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 | 31 +++++++++++++++++++++++--------
boms/tomee-plume/pom.xml | 31 +++++++++++++++++++++++--------
boms/tomee-plus/pom.xml | 31 +++++++++++++++++++++++--------
pom.xml | 2 +-
4 files changed, 70 insertions(+), 25 deletions(-)
