This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch regenerate_boms_after_dep_upgrade
in repository https://gitbox.apache.org/repos/asf/tomee.git
discard f7f9668d14 Minor: Regenerated BOMs for
6ef28be4809f78c601c0edde4aaceed932d44b27
add ce6c128ab2 TOMEE-4468 Smallrye MP Config Impl 3.12.3
add 38c3552bb1 Minor: Regenerated BOMs for
ce6c128ab2cd3af84a04acc948a26abda1c2e1c2
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 (f7f9668d14)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(38c3552bb1)
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 | 6 +++---
boms/tomee-plume/pom.xml | 6 +++---
boms/tomee-plus/pom.xml | 6 +++---
pom.xml | 2 +-
4 files changed, 10 insertions(+), 10 deletions(-)
