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 018dd66b28 Minor: Regenerated BOMs for
e5f88b9826df40befa1ad2662df9f3dfaacea9a7
add d42abb3e0d Bump org.jboss.logging:jboss-logging from 3.6.2.Final to
3.6.3.Final
add d8464d1f3b Minor: Regenerated BOMs for
d42abb3e0d916226d2930108f97fe7319dd4db6e
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 (018dd66b28)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(d8464d1f3b)
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 | 2 +-
boms/tomee-plume/pom.xml | 2 +-
boms/tomee-plus/pom.xml | 2 +-
pom.xml | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
