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 7a6b9d6034 Minor: Regenerated BOMs for
cadc55d58cf384217551b3de90f40f4cf20bf614
add c38de8b21a Bump com.google.code.gson:gson from 2.2.4 to 2.14.0
add 2ed43a48cb Bump version.activemq from 6.2.5 to 6.2.6
add ced85289b4 Bump org.apache:apache from 37 to 38
add 732b1fb3d1 Minor: Regenerated BOMs for
ced85289b447cad9ade4f3cf3b7ea2efb84c38d0
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 (7a6b9d6034)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(732b1fb3d1)
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 | 6 +++---
3 files changed, 15 insertions(+), 15 deletions(-)
