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
discard 941f15df4c Minor: Regenerated BOMs for
c38de8b21a0930101037813ad48ac16e73aeb244
add 2ed43a48cb Bump version.activemq from 6.2.5 to 6.2.6
add 2058828e8a Minor: Regenerated BOMs for
2ed43a48cb88286df567ab6d6b34bc34ef426f80
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 (941f15df4c)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(2058828e8a)
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(-)
