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 d64557c282 Minor: Regenerated BOMs for
2a9c6e221d790f058ae52f647a1c201a816b064e
add 36721d39ee TOMEE-4721 - ActiveMQ 6.3.2 (#3011)
add 46797fcc61 Minor: Regenerated BOMs for
36721d39ee8bf2ba5681284c55f1ddc6e559a71a
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 (d64557c282)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (46797fcc61)
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 | 14 +++++++-------
boms/tomee-plus/pom.xml | 14 +++++++-------
pom.xml | 2 +-
3 files changed, 15 insertions(+), 15 deletions(-)
