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 d0a7613245 Minor: Regenerated BOMs for
a59d24cf17810dc9bcb6cb2183d19d5b87952700
add fe15c310f8 [tomee-10.x]: Bump version.hibernate.orm
add 06ac2dd450 TOMEE-2421 Bump version.microprofile.impl.config (#2421)
add 022cc6db35 Minor: Regenerated BOMs for
06ac2dd450007594c6e70fbf00dffb426f34cc72
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 (d0a7613245)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (022cc6db35)
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 | 16 ++++++++--------
boms/tomee-plume/pom.xml | 16 ++++++++--------
boms/tomee-plus/pom.xml | 16 ++++++++--------
pom.xml | 4 ++--
4 files changed, 26 insertions(+), 26 deletions(-)
