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
omit 8425a24ee9 Minor: Regenerated BOMs for
4d202d8ab5c0e486743c2dcd2a3675a3d9f432e8
add c2140f7440 TOMEE-4694 - [tomee-10.x]: Bump version.activemq from 6.2.9
to 6.2.10 (#2979)
add 2f30a9cceb Minor: Regenerated BOMs for
c2140f744091873b1eedf5a46680b055e68a5bc2
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 (8425a24ee9)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (2f30a9cceb)
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/pom.xml | 12 ++++++------
boms/tomee-plus/pom.xml | 12 ++++++------
pom.xml | 2 +-
3 files changed, 13 insertions(+), 13 deletions(-)
